Bamboo 8.2 upgrade notes
We’ve collected some important notes on upgrading to Bamboo 8.2. For details on all the new features and improvements we’ve introduced in this release, see the Bamboo 8.2 release notes.
Upgrade notes
Here’s some important information you should know about before upgrading.
Lucene index removal
Bamboo no longer indexes data using the Lucene library. The API related to the Lucene index, which was deprecated since version 7.2, has also been removed. Make sure to verify the compatibility of third-party apps with Bamboo 8.2.
Remote agents wrapper support for Apple silicon
Bamboo 8.2 comes with an upgraded Tanuki wrapper providing support for Apple silicon. Remote Agents may require reinstalling the wrapper. For more details, see the Bamboo remote agent installation guide.
Removal of build warning parsers
In this release, we've upgraded the build warning parser library to a newer version that removes Clang-Tidy and RT Tests Parser from the Build warnings parser task.
Changes to custom Elastic Bamboo region configuration
If you use Elastic Bamboo with a custom AWS Region and have modified the Ec2ClientFactoryImpl bean configuration in applicationContextAgentServer.xml, update the configuration and add a signing endpoint to it.
Edit the <BAMBOO_INSTALL_DIR>/atlassian-bamboo/components/bamboo-web-app/src/main/resources/applicationContextAgentServer.xml file by adding the signing region alongside the custom endpoint to the Ec2ClientFactoryImpl bean configuration:
<bean id="awsAccountBean" class="com.atlassian.bamboo.agent.elastic.aws.AwsAccountBeanImpl" plugin:available="true">
<constructor-arg ref="elasticAccountBean"/>
<constructor-arg>
<bean class="com.atlassian.aws.AWSManagerImpl">
<constructor-arg>
<bean class="com.atlassian.aws.Ec2ClientFactoryImpl">
<constructor-arg value="<custom endpoint url>"/>
<constructor-arg value="<custom signing region>"/>
</bean>
</constructor-arg>
<constructor-arg ref="elasticScheduledExecutorService"/>
</bean>
</constructor-arg>
...
</bean>Reusing Elastic Bamboo credentials in the S3 artifact handler configuration
The S3 artifact handler currently doesn't support instance profile credentials. If you configure Elastic Bamboo to use an IAM instance profile, update the artifact handler configuration and provide a separate AWS access key for it.
New Stock Elastic Images
The Stock Elastic Images bundled with Bamboo 8.2 come with a number of breaking changes:
- Only images based on Ubuntu 20.04 LTS and Windows Server 2019 64-bit are provided. The Amazon Linux-based AMI is no longer available.
- Stock AMIs now use HVM virtualization only. Images using PV virtualization are no longer available.
- All images are now EBS-backed. Instance store-backed images are no longer available.
Additionally, all images have a limited set of capabilities. See the following sections for more information.
Ubuntu AMI capabilities
The ‘ec2-user’ account is no longer created on the Ubuntu AMI. If you need to access an EC2 instance started from the image, use the ‘ubuntu’ user account instead.
| Capability | Path |
|---|---|
| Docker | /usr/bin/docker |
| Git | /usr/bin/git |
| JDK 8 | /opt/jdk-8 |
| JDK 11 | /opt/jdk-11 |
| Maven 3.8 | /opt/mvn-3.8 |
Windows AMI capabilities
| Capability | Path |
|---|---|
| JDK 8 | C:\opt\jdk-8 |
| JDK 11 | C:\opt\jdk-11 |
| Maven 3.8 | C:\opt\mvn-3.8 |
| Git | C:\opt\bin\git\git.exe |
If you want to try the new AMIs before upgrading, see the following list:
image.US_EAST_1.EBS.x86_64.linux.HVM.Ubuntu=ami-07272e09cff3e0113
image.ASIA_PACIFIC_NE_1.EBS.x86_64.linux.HVM.Ubuntu=ami-0c23d43955cf2f073
image.AP_NE_2.EBS.x86_64.linux.HVM.Ubuntu=ami-0fcfe40554edc55a2
image.AP_S_1.EBS.x86_64.linux.HVM.Ubuntu=ami-0e645edf0f8b3ab46
image.ASIA_PACIFIC_SE_1.EBS.x86_64.linux.HVM.Ubuntu=ami-068048204d0186b06
image.ASIA_PACIFIC_SE_2.EBS.x86_64.linux.HVM.Ubuntu=ami-0323877238e2add03
image.CA_CENTRAL_1.EBS.x86_64.linux.HVM.Ubuntu=ami-01bfe0d24cd013e3e
image.EU_CENTRAL_1.EBS.x86_64.linux.HVM.Ubuntu=ami-0686bae55e614801f
image.EU_WEST_1.EBS.x86_64.linux.HVM.Ubuntu=ami-0fec35eedef504db5
image.EU_WEST_2.EBS.x86_64.linux.HVM.Ubuntu=ami-09e046949edd3a7fc
image.EU_WEST_3.EBS.x86_64.linux.HVM.Ubuntu=ami-07817a11b970d2776
image.SOUTH_AMERICA_1.EBS.x86_64.linux.HVM.Ubuntu=ami-0f75e9c95801c531a
image.US_EAST_2.EBS.x86_64.linux.HVM.Ubuntu=ami-0124fdc3629ba4f71
image.US_WEST_1.EBS.x86_64.linux.HVM.Ubuntu=ami-0a2a74ba81451c3f9
image.US_WEST_2.EBS.x86_64.linux.HVM.Ubuntu=ami-07adb1b7ce699f577
image.US_EAST_1.EBS.x86_64.windows.HVM.Windows=ami-0419a12ab0085397b
image.ASIA_PACIFIC_NE_1.EBS.x86_64.windows.HVM.Windows=ami-02c26d0ba102f002b
image.AP_NE_2.EBS.x86_64.windows.HVM.Windows=ami-08812173816a7b088
image.AP_S_1.EBS.x86_64.windows.HVM.Windows=ami-01cd060de240f8ab0
image.ASIA_PACIFIC_SE_1.EBS.x86_64.windows.HVM.Windows=ami-042a9ebce3ab3e42e
image.ASIA_PACIFIC_SE_2.EBS.x86_64.windows.HVM.Windows=ami-0ab3874abac07b0fc
image.CA_CENTRAL_1.EBS.x86_64.windows.HVM.Windows=ami-073e82525fa632d48
image.EU_CENTRAL_1.EBS.x86_64.windows.HVM.Windows=ami-019d4f5c593fda3ed
image.EU_WEST_1.EBS.x86_64.windows.HVM.Windows=ami-08304fbdfa5ad0250
image.EU_WEST_2.EBS.x86_64.windows.HVM.Windows=ami-09047d0dceccd11e6
image.EU_WEST_3.EBS.x86_64.windows.HVM.Windows=ami-075f70174eacc9c22
image.SOUTH_AMERICA_1.EBS.x86_64.windows.HVM.Windows=ami-0272319321a35e64e
image.US_EAST_2.EBS.x86_64.windows.HVM.Windows=ami-03ec1ff01a06b892b
image.US_WEST_1.EBS.x86_64.windows.HVM.Windows=ami-01e6ce425afac8574
image.US_WEST_2.EBS.x86_64.windows.HVM.Windows=ami-099d14d1caf21b681If you rely on capabilities that are not present in the new AMIs, you can keep using the old ones. However, because old AMIs won’t receive any security updates, we recommend migrating as soon as possible.
In addition, Stock Elastic Images are no longer guaranteed to be backwards compatible. All breaking changes will still be documented in the version-specific upgrade notes, but you shouldn't rely on installed capabilities or image configuration as they can change with each version. We recommend building your own Elastic Image instead.
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
This release of Bamboo doesn't remove or deprecate support to any of the existing supported platforms.
New supported platforms
This release of Bamboo adds support for the following platforms:
- macOS on Apple Silicon for agents
- Oracle 21c (Oracle JDBC driver version 21 or newer should be used with Bamboo 8.2)
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.