Tasks for AWS 2.20 Upgrade Notes

This page describes known issues as well as changes you should be aware of before deciding whether or not to upgrade to Tasks for AWS 2.20.

Consider testing of app upgrades before rollout into critical production environments

As always, best practices suggest to test each app upgrade in a staging environment before rolling it out to critical production environments.

On this page:

1 Potentially long running upgrade tasks on large instances
2 Potential upgrade issue on remote agents

Related pages:

Tasks for AWS Compatibility Notes

Potentially long running upgrade tasks on large instances

Release 2.20.0 features an upgrade task that re-encrypts credentials stored inline of tasks with the new Bamboo SecretEncryptionService (which replaces the deprecated EncryptionService). While the operation itself is quick, the upgrade task needs to check each task's configuration, which might take a while when upgrading a Bamboo instance with a large number of tasks.

Potential upgrade issue on remote agents

Bamboo might be unable to upgrade apps on running remote/elastic agents:

This long standing upstream issue had been resolved as of Bamboo 5.3. However, there seems to be a regression in Bamboo versions 5.6+, which expose a similar defect.

In case you are affected, this can usually be remedied by restarting the Bamboo server or disabling/reenabling the remote agent.

Please refer to our KB article Unable to execute task due to plugin not being installed for details.