Changes for 5.10
On this page
Stash rebranding information
We've renamed Stash to Bitbucket Server and Bitbucket to Bitbucket Cloud in the Bamboo GUI to maintain consistency with Stash/Bitbucket rebranding.
The changes in the UI don't affect the internal use of APIs.
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 in the upgrade guide.
|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 in the upgrade guide.
|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.|
Dropped support for MySQL storage engines other than InnoDB
|Bamboo 5.10.x runs only with the InnoDB storage engine.|
Security improvements: class serialization
Now you can control the Java classes that are serialized in Bamboo and that are required specifically for Bamboo agent-server communication.
If you have access to the Bamboo home directory, you can edit the whitelist file in the Bamboo configuration directory (<config-dir>/serialization-whitelist.list), which is usually placed in the <bamboo-home>/xml-data/configuration directory.
Plugin vendors can implement a new plugin module to list additional whitelisted classes used by their plugin:
|class that needs to be implemented from Bamboo API||
Example of a configuration directory file
Example of plugin module usage
Other API changes
The following methods were removed without replacement as plugins shouldn't modify the values:
Accessing next build number has been deprecated.
Return type change. The method incorrectly returned
Map<String, Artifact> instead of
This method has been removed.
Method signature changes.
This method has been added. It returns runtime data that complements static task configuration.
Plan directory information REST API
Future changes to on-disk directory layout
A future release of Bamboo will make changes to the layout of the on-disk directory structure for artifacts and logs. These changes are necessary to make functionality more robust. If you are relying on scripts or other tools that examine data in the Bamboo home directory, you will need to update them to ensure that they continue to work.
To make this easier, we have added a resource to the Bamboo REST API to retrieve information about where on disk log files and artifacts will be stored in 5.9 so that you can prepare for the changes.
For more information, see Plan directory information REST API.