Bamboo 7.1 upgrade notes
We’ve collected some important notes on upgrading to Bamboo 7.1. For details on all the new features and improvements we’ve introduced in this release, see the Bamboo 7.1 release notes.
Here’s some important information you should know about before upgrading.
Synchronizing remote agent capabilities
The Bamboo team is happy to address a long awaiting issue of synchronizing remote agent capabilities. Starting from version 7.1 modifying a remote agent capability in the
bamboo-capabilities.properties will also modify that capability in Bamboo. Capabilities synchronisation occurs when an existing agent reconnects to the Bamboo server So modifying
bamboo-capabilities.properties file requires restarting the agent to update the capabilities.
After upgrading Bamboo to 7.1 all remote agents' capabilities will have an unknown source. Upon the agent's first reconnection, Bamboo will try to upgrade of the capabilities sources. If a capability's key and value match capability from the auto-detection or the properties file then Bamboo will set them as the source. Otherwise Bamboo will set UI as the capability source (so no capabilities will be removed during the upgrade).
Docker Runner: the default arg --net=host removed
Prior to 7.1, Bamboo started docker containers with --net=host argument by default. In 7.1 this argument has been removed. This can impact builds that assume certain networking conditions (e.g. connecting to a service, database). Extra docker run args can be provided in plan configuration.
Remote agents workspace cleanup
As of version 7.1, build and deployment workspaces are removed from remote agents' home directories if corresponding entities are removed on Bamboo server. In case of agents with long build history, the cleanup happens gradually, in order to avoid agent unresponsiveness upon upgrade.
Upgrade of the org.quartz-scheduler library
In Bamboo 7.1 we’ve upgraded the org.quartz-scheduler library from version 2.1.7 to 2.3.2. As a result, certain Bamboo settings (cron expression) might stop working and you might have to reenter them manually.
Lucene dependency was upgraded to 7.7.3. Old indexes are incompatible with this version and will be automatically removed at instance startup. Background reindex job will be scheduled as well. While indexes are being recreated some features like quick search or reports will not work correctly. Some apps might be affected by this change.
Ant dependency was upgraded to 1.10.8. Some apps which work with custom artifact handlers might be affected.
CVS not supported
Starting from Bamboo 7.1, CVS repositories are not supported anymore.
This release of Bamboo does not introduce any changes to supported platforms. For more information about what the latest stable release of Bamboo supports, see Supported platforms.
How to upgrade Bamboo
See the Bamboo upgrade guide for a complete walk-through of the upgrade process that includes descriptions of all the available upgrade paths, prerequisites, and methods.