Version-specific upgrade notes

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

The version-specific notes provide additional information to the main upgrade documentation. We recommend reading the version-specific notes for the original and new Bamboo instance versions.

Upgrading to Bamboo 8.2

Jump to the section that you're interested in:

Changes to what Bamboo supports

Here's a summary of changes to supported platforms. For more information about what Bamboo supports, see Supported platforms.

Operating systems

Added support for macOS on Apple silicon for agents.

Databases

Added support for Oracle 21c (Oracle JDBC driver version 21 or newer should be used with Bamboo 8.2).

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.

CapabilityPath
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

CapabilityPath
JDK 8C:\opt\jdk-8
JDK 11C:\opt\jdk-11
Maven 3.8C:\opt\mvn-3.8
GitC:\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-099d14d1caf21b681

If 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.

See the list of previous Stock Elastic Images...

Previous Stock Elastic Images

image.SOUTH_AMERICA_1.EBS.x86_64.linux.HVM.Ubuntu=ami-00bab8ad610da4553
image.EU_CENTRAL_1.EBS.x86_64.windows.HVM.Windows=ami-01b73865630e3deba
image.EU_WEST_3.EBS.x86_64.linux.HVM.Ubuntu=ami-028689636c1f3a3cd
image.SOUTH_AMERICA_1.EBS.x86_64.linux.PV.Ubuntu=ami-06782ef03a5dca332
image.US_WEST_1.EBS.x86_64.linux.PV.Ubuntu=ami-01b9aa8cbbf3c72d0
image.SOUTH_AMERICA_1.EBS.x86_64.windows.HVM.Windows=ami-06f2edb4be01f7b3b
image.US_EAST_1.EBS.x86_64.linux.PV.Ubuntu=ami-0e975b039b9a03733
image.US_EAST_1.S3.x86_64.linux.PV.Amazon\ Linux=ami-052968d3b353588da
image.EU_WEST_3.EBS.x86_64.windows.HVM.Windows=ami-07d02d4c7e16f7469
image.ASIA_PACIFIC_SE_2.EBS.x86_64.linux.HVM.Ubuntu=ami-070712671b8efbc13
image.ASIA_PACIFIC_NE_1.EBS.x86_64.linux.PV.Ubuntu=ami-0ab64817dcbea766e
image.AP_NE_2.EBS.x86_64.windows.HVM.Windows=ami-0618b71bac827fb75
image.US_EAST_2.EBS.x86_64.windows.HVM.Windows=ami-020d8fb1648e3c7a5
image.US_EAST_1.EBS.x86_64.linux.HVM.Ubuntu=ami-051b79bf05cbe7288
image.US_WEST_2.EBS.x86_64.windows.HVM.Windows=ami-0d74da69232892fe2
image.AP_S_1.EBS.x86_64.windows.HVM.Windows=ami-0e24b0815f64c39b6
image.AP_S_1.EBS.x86_64.linux.HVM.Ubuntu=ami-0bbd55ae98972e42b
image.EU_WEST_2.EBS.x86_64.linux.HVM.Ubuntu=ami-0a5a9fbb673c800f2
image.EU_WEST_2.EBS.x86_64.windows.HVM.Windows=ami-0d6fff1df11f819ab
image.US_WEST_2.EBS.x86_64.linux.PV.Ubuntu=ami-0506a992231fef72e
image.US_EAST_1.EBS.x86_64.windows.HVM.Windows=ami-006187e1d05ab1fc3
image.US_WEST_1.EBS.x86_64.windows.HVM.Windows=ami-0c9831a604359f14e
image.ASIA_PACIFIC_SE_1.EBS.x86_64.linux.HVM.Ubuntu=ami-0139d72b1df4fc9de
image.CA_CENTRAL_1.EBS.x86_64.windows.HVM.Windows=ami-0e0e000555f2e0ef6
image.US_WEST_2.EBS.x86_64.linux.HVM.Ubuntu=ami-0939b6b8733030be1
image.EU_WEST_1.EBS.x86_64.windows.HVM.Windows=ami-0f4561c3e24e3cd6c
image.ASIA_PACIFIC_SE_1.EBS.x86_64.linux.PV.Ubuntu=ami-0a576f2ed2044873c
image.ASIA_PACIFIC_NE_1.EBS.x86_64.linux.HVM.Ubuntu=ami-002b4da51b1634de5
image.ASIA_PACIFIC_SE_2.EBS.x86_64.windows.HVM.Windows=ami-0b342a2ba79532fb6
image.AP_NE_2.EBS.x86_64.linux.HVM.Ubuntu=ami-04852c15c66501306
image.EU_WEST_1.EBS.x86_64.linux.HVM.Ubuntu=ami-00f1b5d5dc4f1f557
image.US_EAST_1.EBS.x86_64.linux.PV.Amazon\ Linux=ami-0207018e91a500945
image.EU_CENTRAL_1.EBS.x86_64.linux.HVM.Ubuntu=ami-04f60e45619e90542
image.ASIA_PACIFIC_NE_1.EBS.x86_64.windows.HVM.Windows=ami-0c63a7a102bbbd34b
image.CA_CENTRAL_1.EBS.x86_64.linux.HVM.Ubuntu=ami-0ddafd7ea4808e5f8
image.US_WEST_1.EBS.x86_64.linux.HVM.Ubuntu=ami-081e1e23d6d42d359
image.ASIA_PACIFIC_SE_1.EBS.x86_64.windows.HVM.Windows=ami-064a59d05cc453c50
image.US_EAST_2.EBS.x86_64.linux.HVM.Ubuntu=ami-0867cb35edc82cfae
image.EU_CENTRAL_1.EBS.x86_64.linux.PV.Ubuntu=ami-0b7da87b1cd844938
image.ASIA_PACIFIC_SE_2.EBS.x86_64.linux.PV.Ubuntu=ami-09d54d5ab600b9bf3
image.EU_WEST_1.EBS.x86_64.linux.PV.Ubuntu=ami-05d2975fd3db2e87d













Last modified on Jul 20, 2022

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.