Bamboo 5.10 EAP developer notes
Atlassian is proud to present Bamboo 5.10 EAP. This public development release is part of our Early Access Program (EAP) leading up to the official Bamboo 5.10 release. We are making these EAP milestones publicly available so that developers can start assessing the impact of the changes that we are making.
It is our intention to notify you, our plugin developers, as far in advance as possible of everything we know that could possibly affect your plugins. We will update this page as the release progresses, so please watch this page or check back regularly to keep on top of the changes.
Summary of changes
We're introducing the following changes:
|JDK8 as a minimum runtime and compile requirement||
Bamboo 5.10.x doesn't run or compile on JDK less than 8.
Plugin developers can now use all new shiny Java 8 goodies including streams and lambdas.
|Bamboo runs on Tomcat 8||
Bamboo 5.10.x runs on Tomcat 8.
For more information about upgrading your project configuration, see Starting Bamboo and running integration tests.
|Servlet API upgrade (3.0.1)||
Bamboo 5.10.x runs on Tomcat 8 and therefore provides servlet API 3.0. Make sure that your plugin is compatible with the servlet API 3.0.
For more information, see Building plugins against custom versions of Bamboo.
|Plugins framework (4.0.4)||
This is an upgrade of the way in which Bamboo transforms and loads plugins.
|SAL upgrade (3.0.2)||
For more information, see SAL 3.0 Upgrade Guide.
Soy Renderer upgrade
The new soy compiler used by Bamboo is more restrictive when it comes to the template syntax. Make sure that your templates are properly compiling in runtime.
|REST 3.0 upgrade||We've upgraded REST to 3.0.2.|
Bamboo 5.10 EAP upgrade guidelines
Follow the guidelines below and see the Known issues section to prepare for the upgrade.
Building plugins against custom versions of Bamboo
To simplify testing against new Bamboo and maintain backwards compatibility, make sure that the plugin POM imports the component versions from
Your dependencies shouldn't override the artifacts versions defined by Java Platform and should use the
bamboo.version property to specify the version of Bamboo to compile against.
Testing compile-time compatibility with Bamboo is as simple as:
Starting Bamboo and running integration tests
To start Bamboo and run integration tests against Bamboo 5.10, AMPS needs to be instructed to run Tomcat 8 as a container with the
containerId configuration parameter:
Then running integration tests is as simple as:
In case of more complicated POMs, you might consider using POM profiles to separate dependencies and AMPS configuration.
Specific test dependencies
If your plugin tests contain WebDriver or wired tests, it should use the following dependencies:
Manual plugin tests
If the plugin has no integration test or if you just want to run Bamboo with the plugin loaded, use:
The features won't cause any breakages and will be announced with the official Bamboo 5.10 release.
If you change repository details (including authentication) in the plan, the information is not propagated to all plan branches.
You shouldn't revoke the existing keys in Bitbucket Server and use Bamboo to create new ones or your existing plan branches will stop working.