Bamboo 11.0 upgrade notes

Bamboo release notes

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

We’ve collected some important notes on upgrading to Bamboo 11.0. For details on all the new features and improvements we’ve introduced in this release, see the Bamboo 11.0 release notes .

Upgrade notes

Here’s some important information you should know about before upgrading.

All Bamboo nodes must run under the same user

In a clustered Bamboo High Availability (HA) setup with multiple nodes, it's essential that all nodes operate under the same single user account. This practice is crucial for mitigating potential security risks. Starting from version 11.0.0, Bamboo won’t function properly if this requirement isn’t met. Ensure UID and GID synchronization across nodes to prevent permission issues, especially in NFS or CIFS setups without local username mapping.

Migration to Struts 6

We’ve upgraded to Struts 6. Make sure you’re aware of the following changes:

  • Annotate getters with @StrutsParameter(depth=X) (dependency on struts-corelib)

  • Annotate setters with @StrutsParameter (dependency on struts-corelib)

  • The action method previously named doSomething must now be fully informed. Previously, the do prefix could be suppressed.

  • The method previously named getBamboo() has been renamed to getBambooContainer() to avoid warnings from Struts when .bamboo. is used in our templates.

  • OGNL Allowlist.

You can find extensive documentation on how to apply these changes at Struts Module

Bamboo uses the AWS SDK V2 now

Bamboo AWS-related functionality, such as elastic agents and S3 artifact handlers, are now using AWS SDK V2, which replaced V1. This change was introduced to elevate your security and improve the performance and it should be invisible from the user perspective.

CodeDeploy Task was removed

After being deprecated for some time, the AWS CodeDeploy Task was finally removed from Bamboo due to compatibility and security concerns.

Legacy repositories API is removed

Bamboo 11.0 has removed the legacy repositories API. This change finalizes the transition to the modern API introduced in Bamboo 5.14, which included a rebuilt repository subsystem, new plugin points, and web repository viewers. This update eliminates technical debt and ensures a more streamlined and efficient system. Check out Bamboo API Changes for 5.14for more details.

Introducing Deployments Cache

Bamboo 11 introduces the global deployment projects and environments cache, which speeds up user interactions and background processing. We highly recommend having it enabled. However, the environments' cache can be disabled by setting the system property bamboo.deployment.cache.enabled to false.

Quiet period was removed

The quiet period functionality has been removed due to performance issues. Consider using the Stop oldest builds strategy for concurrent builds as an alternative. Explore more: Configuring concurrent builds | Bamboo Data Center 10.2 | Atlassian Documentation

Optional disabling of Change Detection for Branches from Forked Pull Requests

Bamboo now allows you to manage performance by optionally disabling change detection for branches created from forked repositories. This feature, enabled by the Create plan branch strategy set to Forked repositories are allowed, can impact performance. If you’re not using this functionality, we recommend disabling it to save resources. Set the system property bamboo.disable.bbdc.change.detection.for.prs.from.forked.repos to true to enhance Bamboo's performance by reducing the load on event workers.

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:

(warning) PostgreSQL 14

In this release, we’re deprecating support for:

(warning) PostgreSQL 15

(warning) SQL Server 2017

(warning) MySQL 8.0

(warning) Java 17

We are actively working on adding support for MySQL 8.4

New supported platforms

Bamboo 11.0 doesn’t introduce support for any new software platforms.

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.

Last modified on Apr 30, 2025

Was this helpful?

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