Bamboo 9.1 release notes

Bamboo release notes

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

December 2022

We’re proud to present Bamboo 9.1.

Take some time and read through the release notes to learn what we've prepared for you this time. Swing by the upgrade notes to check for any breaking changes if you plan to upgrade and don’t forget to check out the full list of resolved issues.

Optimized performance and reliability

We’ve worked hard to make sure that Bamboo is fast, responsive, and reliable by introducing a whole slew of improvements.

Reduced resource usage with the new SFTP artifact handler


We’ve added a new artifact handler that uses the SFTP protocol for transferring build artifacts to and from a dedicated SSH storage server. This reduces resource usage on the Bamboo server and improves its performance by delegating all the heavy lifting to the remote server.

The SFTP artifact handler supports both on-premise and cloud-based storage servers located in a cloud of your choice.

Learn more about the SFTP artifact handler.

Faster deployment data collection


We've improved the performance of deployments-related REST API endpoints and UI views. Now, the results are returned faster and the response time is less dependent on the size of your Bamboo instance. 

Artifacts travel at greater speeds


The Bamboo server and SFTP artifact handlers gained a package threshold option that lets you set the maximum allowed number of files per artifact. When the number of files in artifacts exceeds this threshold, they are compressed into a .zip archive.

This feature prevents artifacts with many files from causing performance bottlenecks.

Enhanced security

Since security is often our customers' highest priority, this release provides new solutions to safeguard your network and data.

Allow external applications to control Bamboo through OAuth 2.0


We’ve added support for incoming app links, allowing Bamboo to act as an OAuth provider for third-party applications. Linked apps can be granted limited or full access to Bamboo data on behalf of a Bamboo user with respect to the user’s permissions. Additionally, because access authorization happens over OAuth 2.0, exchanging data between applications is always secure and reliable. 

At the same time, we’re working on adding support for outgoing links to third-party applications in a future release. Keep an eye out for further updates.

Learn more about OAuth 2.0 support.

Developer productivity

There are a bunch of new features that’ll make your work as a developer easier and more productive.

Support for pull requests from GitHub repositories


Bamboo can now detect pull requests originating from directly cloned and forked GitHub repositories. You can enable this feature from the plan configuration page or configure it with Bamboo Specs.

Learn more about automatic branch management and how to configure new branch handling with Bamboo Specs.

Bamboo YAML Specs validator  


Instead of verifying or troubleshooting your Bamboo YAML Specs configuration by repeatedly pushing changes to the source code, you can now quickly and reliably fine-tune and validate your YAML Specs with the new YAML Specs validator.

The validator can check your YAML Specs configuration against a specific repository and it’ll also check for any syntax errors following the Bamboo YAML Specs format.

Learn more about the Bamboo YAML Specs validator.

Audit log content is now searchable


You can now search for a specific term in the audit logs to find the data you’re looking for much faster. Bamboo supports search in all kinds of audit logs: global, plan, deployment project, and agent logs.

Resolved issues

This is a summary of the issues we’ve resolved throughout the lifecycle of Bamboo 9.1.

Issues resolved in Bamboo 9.1.3
Released on .

T Key Summary Status

Issues resolved in Bamboo 9.1.2
Released on .

In this release, we’ve fixed a bug affecting jobs running inside a Docker container. If Bamboo couldn't clean a job's working directory because the working directory was inaccessible from within the container, Bamboo would delete the entire contents of the Docker runner container including attached volumes.

From now on, to protect the contents of attached Docker volumes, the Clean working directory task will fail if the job’s working directory is inaccessible. However, if the Clean working directory after each build option has been selected and the action can’t be completed, the job will complete successfully, but the contents of the working directory won’t be removed.

T Key Summary Status

Issues resolved in Bamboo 9.1.1
Released on

T Key Summary Status

Issues resolved in Bamboo 9.1.0
Released on

This release fixes a bug where restarting Bamboo while a build triggered from Bitbucket Data Center or Server was still running resulted in the build status in Bitbucket getting stuck in In progress indefinitely. However, the fix increases the minimum release of Bitbucket Data Center and Server supported by Bamboo.

From now on, Bamboo can integrate with Bitbucket Data Center and Server 7.5 or newer only. If you’re running an older release of Bitbucket Data Center or Server, consider upgrading your Bitbucket instance before upgrading to Bamboo 9.1.0.

T Key Summary Status

Last modified on Feb 1, 2024

Was this helpful?

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