Bamboo 10.0 release notes
Highlights
- Bamboo 10.0.0
- Upgrade to Atlassian Data Center Platform 7
- Dark theme is here!
- REST v2 API updates
- WebSudo support
- New default endpoint security annotations
- New execution strategy for concurrent builds
- Improved GitHub integration
- AWS IMDSv2 support for Elastic Agents
- Enhanced encryption for Bamboo Server-Agent communications
- Simplified test case processing
- Build number modification
- Announcement banner
- Configuring the allowlist
- Triggering a build after a successful deployment
- Before you upgrade to Bamboo 10.0
- Known issues
- Resolved issues
Bamboo 10.0.0
Release date:
Here's what's new in Bamboo 10.0.0.
Upgrade to Atlassian Data Center Platform 7
Bamboo 10.0 includes an upgrade to Atlassian Platform 7. This upgrade improves the quality of our response to security changes with reduced disruption and breaking changes for Atlassian Marketplace apps.
As part of the upgrade to Platform 7 and with the focus on enhanced security and performance, we’ve made the following updates:
Upgraded numerous Atlassian and third-party components to benefit from the latest security patches and bug fixes
Removed ‘gray APIs’ (unsupported third-party and cross-product libraries with their dependencies)
Reduced public JAVA API in Atlassian Plugins, Web Resource Manager (WRM), Web Fragments, and LESS.
Explore how to prepare for the Atlassian Platform 7 upgrade
Dark theme is here!
Bamboo 10.0 now supports both dark and light themes, offering a modern visual experience.
To enable dark theme, select your profile picture in the upper-right corner of the screen. From there, select Theme, and then Dark. The original theme will be phased out in future releases. Note that custom header colors will automatically switch to the light theme.
If your app incorporates visual elements, developers should check our guidelines on how to prepare Data Center app for the dark theme, and designers should explore how to utilize tokens.
REST v2 API updates
Platform 7 and Bamboo 10.0 have rearchitected the Java APIs used to implement REST resources, which we’re calling REST v2.
These changes will only impact Marketplace partners who develop apps. The underlying libraries, Jackson and Jersey, have been upgraded to the latest versions. REST v2 also makes use of JAX-RS 2.
Check out the RESTv2 migration guide
WebSudo support
Bamboo 10.0 adds support for WebSudo to further protect admin pages against malicious access. This feature creates an extra layer of protection by prompting admins to re-enter their passwords to access administrative functions.
Apps can opt into WebSudo by adding the @WebSudoRequired
annotation to REST APIs that require admin access. Similarly, servlets that require admin access should call WebSudoManager.enforceWebSudoProtection
.
Discover how to add WebSudo support to your app
New default endpoint security annotations
We’ve enabled a new set of annotations to improve endpoint security by giving you better control over access to endpoints. The revised annotations allow only the intended users to access your application endpoints.
Important annotations to review:
@AdminOnly
@AnonymousSiteAccess
@LicensedOnly
@SystemAdminOnly
@UnlicensedSiteAccess
@UnrestrictedAccess
From Bamboo 10.0, when no annotation is specified, only licensed users will be able to access resources. You may need to modify endpoints such as Struts Actions, Filters, Servlets, and REST resources.
Check out how to prepare your Data Center app for secure endpoint compliance
New execution strategy for concurrent builds
When configuring the concurrent builds limit, you can decide either to block the build requests or allow them by stopping the oldest builds to maintain the limit. This feature ensures that the latest commits are always built while keeping resource usage within your specified limits.
Explore how to configure the execution strategy to stop oldest builds
Improved GitHub integration
Bamboo 10.0 now sends build statuses directly to GitHub out of the box. This allows you to view build results on GitHub, use these results to protect your branches, and access Bamboo directly from GitHub. Additionally, Bamboo now supports shared credentials when configuring GitHub repositories, enhancing repository management security and convenient setup.
Check out more details about GitHub improvements
AWS IMDSv2 support for Elastic Agents
In response to customer feedback, Bamboo 10.0 now supports Instance Metadata Service Version 2 (IMDSv2) for Elastic Agents. IMDSv2 enhances security by introducing a session-oriented approach for AWS Elastic Compute Cloud (EC2) metadata retrieval, significantly reducing the risk of unauthorized access.
Note that this enhancement applies exclusively to stock images or those customized from our stock images. To ensure backward compatibility and broader support, IMDSv1 remains available as a fallback mechanism.
This update provides users with a reliable method to safeguard their Elastic Agents within AWS EC2 environments.
Enhanced encryption for Bamboo Server-Agent communications
With the release of Bamboo 10.0, we’ve enhanced the encryption protocols used to exchange information between the Bamboo server and its Agents. This upgrade reinforces our commitment to safeguarding sensitive information, such as passwords and SSH keys, against unauthorized access without altering the user experience. The implementation seamlessly integrates into existing workflows, ensuring an uninterrupted and secure process for all users.
Simplified test case processing
Tracking the entire history of a large number of test cases slows down the processing of build results and increases database load.
With reduced history tracking, you can enhance the system performance by keeping important data about test cases that failed and excluding those that were completed successfully. Bamboo also keeps the reduced subset of test case metadata. As a per-job setting, this feature helps achieve faster build results and save computation resources, allowing Bamboo to allocate resources more efficiently.
Check out how to disable tracking of full history of test cases for a job
Build number modification
With Bamboo 10.0, you can modify the next build number for a plan or plan branch. This is useful, for example, when a build administrator wants to change the Bamboo build number to maintain continuity when migrating from other continuous integration systems.
Modify the next plan build number
Announcement banner
Bamboo 10.0 allows administrators to configure an announcement banner, similar to other Data Center products. Use this feature to inform users about upgrade windows, existing issues, or any other important information you want to share.
Configuring the allowlist
With Bamboo 10.0, administrators can now manage outgoing connections by adding URLs to an allowlist, enhancing security and testing connections for the following repositories:
Git
GitHub
Bitbucket Cloud
Bitbucket Data Center
Application links are automatically included, and SSH connections require specific regular expressions. Due to security risks, we don’t recommend disabling the allowlist. Explore how to configure the allowlist
When connecting to Bitbucket Data Center, Bamboo adds an SSH entry with the default port 7999. If you're using a custom SSH port, then manually modify the entry.
Triggering a build after a successful deployment
With Bamboo 10.0, you can now schedule builds to run automatically after a successful deployment. Configure this for deployments originating from a specified environment or any environment within the chosen deployment project. This feature enables an automated workflow from deployments to builds.
Check out how to trigger a build after a successful deployment
Before you upgrade to Bamboo 10.0
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.
In this release, we’ve made significant changes in our core architecture to increase security and performance. Before upgrading, visit the Bamboo 10.0 upgrade notes to review important upgrade steps and see the full list of issues resolved.
Known issues
This section contains information about any issues that we’ve discovered in our testing. We’re constantly keeping an eye out and if we find anything, we’ll let you know right here.
Issue with custom SSH port configuration when linking to Bitbucket Data Center
When connecting to Bitbucket Data Center, Bamboo automatically adds an SSH entry with the default port 7999. If your setup uses a custom SSH port, you must manually modify the entry to reflect your specific port configuration.
Check out how to modify an SSH port
BAM-25869 - Getting issue details... STATUS
Resolved issues
Scroll through the list of the issues we’ve resolved throughout the lifecycle of Bamboo 10.0.