Bamboo 10.2 upgrade notes
We’ve collected some important notes on upgrading to Bamboo 10.2. For details on all the new features and improvements we’ve introduced in this release, see the Bamboo 10.2 release notes.
Skip to
Upgrade notes
IMPORTANT
Platform releases allow us to incorporate multiple significant changes (often called “breaking changes”) that aren't compatible with previous versions. These changes establish a strong foundation for more extensive development in future releases.
To increase security and performance, we’ve made changes in our core architecture that require apps to bundle their libraries. We're collaborating with our marketplace partners on these changes, however, some apps may not be immediately compatible with the new platform upon release.
We recommend that you review your apps before upgrading to avoid service disruptions for your organization.
To check app compatibility, visit Checking app compatibility with application updates, or the Atlassian Marketplace to see if your app hosting is compatible with your product version.
Bamboo 10.2 is a long-term support (LTS) release. Normally, we don’t introduce new features in LTS releases but rather consolidate the ones' we’ve introduced since the last LTS release (Bamboo 9.6).
This summary has been divided into sections that group the changes by severity and type:
Breaking changes
Learn about what you need to keep an eye on to avoid outages or disruptions. The entries in this section are organized chronologically from newest to oldest:
NEW IN THIS RELEASE Elastic Instances (and remote agents) needs to be restarted after updating from 9.2 (java incompatibility)
The support for Java 11 was deprecated in Bamboo 9.6 and removed in Bamboo 10,. The new agents and elastic instances are now based on Java 17. If you are coming from Bamboo 9.2, your agents and elastic instances are still based on Java 11 and must be restarted.
Take a look at Supported platforms for more information about what platforms are supported by this LTS release.
NEW IN THIS RELEASE Permissions for Deployment projects
We revisited the deployment project permissions and introduced the following changes:
New
CREATE_RELEASEpermissions that let you create deployment releases. It depends on theREADpermission.New
CLONEpermission that let you clone deployment projects. It depends on the READ andVIEW_CONFIGURATIONpermissions.New
ADMINISTRATIONpermission that lets you do anything on the deployment project and automatically grants all other permissions.EDITpermission doesn't let you delete deployment projects anymore; you needADMINISTRATIONfor this.EDITpermission doesn’t depend onAPPROVE_RELEASEany longer. That means you can haveEDITbut still not be able to approve releases. TheAPPROVE_RELEASEpermissions need to be granted separately.
The existing permissions will be migrated automatically, but specs that handle these permissions must be adapted after upgrade to the changes described above.
10.0 AWS IMDSv2 support for Elastic Agents
To protect against unauthorized data access, Bamboo 10.0 includes support for AWS Instance Metadata Service Version 2 (IMDSv2). This change enhances the security of Elastic Agents on EC2 by using a session-based approach to access instance metadata. The Ubuntu image is based on Ubuntu 24.04 LTS, and the Windows image is based on Windows Server 2022.
IMDSv2 is supported for both stock and customized images. Since AWS has disabled IMDSv1 on their stock Ubuntu 24.04 image, we've also disabled IMDSv1 on our stock Ubuntu and Windows images starting with Bamboo 10.0. To enable IMDSv1, you'll need to create a customized image based on the stock image and enable IMDSv1. We recommend customization for all users, as stock images don't guarantee backward compatibility.
Discover more information about stock images
10.0 New login URI
Bamboo 10.0 introduces a new login URI. While an HTTP redirection rule is in place to handle this change, automated scripts might not process HTTP 301/302 responses correctly. We recommend updating any scripts interfacing with the login URI to point from <BambooURL>/userlogin!doDefault.action to <BambooURL>/userlogin.action.
Additionally, Bamboo Docker images may be affected by this URI change. If you're using customized Docker images, recreate them using the latest Bamboo 10.0 Docker image for compatibility.
Improvements, fixes, and non-breaking changes
Get a glimpse of all the improvements, fixes, and non-breaking changes added to each release leading up to Bamboo 10.2. The table is divided into rows by release. Every row contains a link to the relevant upgrade notes where you can learn the details.
Release | Description | Upgrade notes link |
|---|---|---|
10.1 |
| |
10.0 |
| |
9.6 |
|
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:
Java 11 (Bamboo 10.0)
PostgreSQL 12 (Bamboo 10.0)
PostgreSQL 13 (Bamboo 10.1)
Oracle 18c (Bamboo 10.0)
Perforce (Bamboo 10.0)
In this release, we’re deprecating support for:
PostgreSQL 14 (Bamboo 10.1)
Support for the deprecated features and platforms will be removed entirely in a future version of Bamboo.
Check all End of support announcements.
New supported platforms
In this release, we’ve added support for:
Java 21 (Bamboo 10.1)
PostgreSQL 17 ((Bamboo 10.1)
How to upgrade Bamboo
Before you upgrade, check app compatibility by visiting Checking app compatibility with application updates, or the Atlassian Marketplace to see if your app hosting is compatible with your product version.
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.