Bamboo 9.5 upgrade notes
We’ve collected some important notes on upgrading to Bamboo 9.5. For details on all the new features and improvements we’ve introduced in this release, see the Bamboo 9.5 release notes .
Skip to
Upgrade notes
Here’s some important information you should know about before upgrading.
End of support for Server licenses
Bamboo 9.5 is the first Data Center-only release and doesn’t support Server licenses. If you have a Server license, learn more about your options.
With Atlassian Server end of support, you’ll need to ensure you have a valid Data Center license before upgrading to Bamboo 9.5. Learn how to update your Bamboo license
Bamboo 9.4.x will continue to support Server licenses until February 15, 2024. Learn more about your options
Migrate to warm standby before starting Bamboo 9.5
This version of Bamboo introduces warm standby clustered deployments. If you're already using Bamboo Data Center in a cold standby cluster configuration, you’ll need to migrate to the new warm standby configuration before starting Bamboo 9.5 for the first time after the upgrade.
Learn how to migrate to a warm standby clustering configuration
- It’s not possible to run different versions of Bamboo in the same cluster. Make sure to match the versions of Bamboo running on each cluster node.
- It’s not possible to downgrade to an older version of Bamboo. To revert back to a previous version, restore it from the last backup or snapshot (including the database).
Changes to the internal database structure during the upgrade
During the upgrade to version 9.5, Bamboo needs to make extensive modifications to the internal structure of the database. This means that if your Bamboo instance contains millions of deployment projects, release versions, or test results, you should allow several hours for the upgrade to complete.
Regenerate database access credentials due to updates to the atlassian-passwords library
The atlassian-passwords library has been renamed to atlassian-secrets and updated to support more ciphers and secret providers. The update also renames several packages and introduces support for Tomcat HTTPS connectors.
As a result, we’ve replaced the atlassian-bamboo-tomcat-util library with atlassian-secrets. However, this means that you’ll have to make some changes to configuration files and regenerate your passwords and keys.
If you use advanced database password encryption:
- In the
bamboo.cfg.xml, rename the cipher classes as follows:- Change
com.atlassian.db.config.password.ciphers.algorithm.AlgorithmCiphertocom.atlassian.secrets.store.algorithm.AlgorithmSecretStore. - Change
com.atlassian.db.config.password.ciphers.base64.Base64Ciphertocom.atlassian.secrets.store.base64.Base64SecretStore.
- Change
Regenerate the password using the new atlassian-secrets library in the
/tools/atlassian-passworddirectory:java -jar atlassian-secrets-cli.jar -config=db
If you encrypt passwords in server.xml:
- In the
server.xmlfile:- Rename
com.atlassian.bamboo.tomcat.utilstocom.atlassian.secrets.tomcat.protocol. - Replace the
bambooEncryptionKeyproperty with theproductEncryptionKeyproperty.
- Rename
Regenerate keys using the atlassian-secrets library in the
/tools/atlassian-passworddirectory:java -jar atlassian-secrets-cli.jar -config=tomcat
Changes to the Bamboo REST API
Due to the implementation of warm standby and support for native avatars, we’ve had to make some changes to the Bamboo REST API.
The response payload of the rest/api/latest/server/* endpoint has changed:
- The
statefield has been renamed toaskedNodeState - The
clusterStatefield has been added - The
setByUserfield has been removed
Additionally, the payloads of all resources except the new rest/api/latest/avatar/user will no longer contain the URL to the user’s Gravatar. To programmatically obtain the user’s native avatar file or the Gravatar URL, call the rest/api/latest/avatar/user endpoint.
To maintain smooth caching and optimize avatar retrieval when using a load balancer that filters headers, configure your load balancer to pass the "If-Modified-Since" header from the client browser to Bamboo nodes. Without it, your servers might unnecessarily transmit unchanged resources, impacting performance.
If you're using a proxy such as nginx with caching enabled, disable caching just for the avatar REST endpoints (/rest/api/latest/avatar/*) to prevent the proxy from returning outdated avatars. Bamboo handles avatar image caching on its own.
Changes to supported platforms
See what changes are in store for the supported platforms in Bamboo. For more information about what the latest stable release of Bamboo supports, see Supported platforms .
End-of-support announcements
In this release, we’re removing support for:
Postgres 11
Oracle 12C
MySQL 5.7
In this release, we’re deprecating support for:
Postgres 12
Java 11 for the Bamboo server and agents (How to upgrade the Java version used by Bamboo)
Clover integration
Support for the deprecated features and platforms will be removed entirely in a future version of Bamboo.
New supported platforms
This release of Bamboo doesn't add support for any new software 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.