Bamboo 6.3 release notes
Bamboo YAML Specs
As an alternative to using Bamboo Java Specs, Bamboo 6.3 allows you to create simple plans using Bamboo YAML Specs in no time. Just use one of the templates we provide and you're ready to start committing your files to a repository.
To learn more about this feature, see Bamboo YAML documentation. We've also prepared a number of templates that you can use in our Bamboo YAML reference.
New repository-stored Bamboo Specs protection
You can now process repository-stored Bamboo Specs in a Docker container for extra security. Docker gives you an opportunity of running builds in an isolated environment available only for the duration of the build. Bamboo 6.3 is shipped with a Docker image that contains alle required dependencies.
Bamboo 6.3 adds new permission controls for linked repositories. User is now able to choose what RSS repository can use a given repository or grant all repositories access for RSS repository.
In case build plan or deployment project try to use repository which was not granted these permissions, a build will fail and user will get information in RSS logs that repository usage is not allowed.
Branching with multiple repositories
This highly-anticipated feature allows you to change individual branches for all repositories in your plan, regardless whether the branch was created manually of automatically. In Bamboo 6.3 you will also be able to override any repository settings such as repository location, which might come in handy in case your development workflow uses forks rather than branches. To learn more, check out Using plan branches.
To make your life easier, we've also added a quick overview of repositories and branches used in the plan—Repository branches on the Branch details tab.
Cleaning up permission dependencies
To ensure the consistency of Bamboo permissions, starting with Bamboo 6.3, we provide an update mechanism which will fix all inconsistencies for all permissions in your Bamboo environment. We have also modified all the pages where you can edit permissions in a way that won’t allow granting inconsistent or clashing permissions in the future.
From now on, if you want to revoke a lower-level permission for a user, you must revoke the higher-level permissions first. Also, when granting a higher-level permission to a user, all relevant lower-level permissions will be granted automatically to that user.
Starting from version 6.3, Bamboo is able to pick up your variables from all fields of a task or deployment. You can find everything you want to know about variables in Bamboo in our documenation.
Git authentication more secure
For any Git operation that require authentication, Bamboo 6.3 introduced new way of storing your credentials. Your user name and password are now kept in a temporary file created by Bamboo. Once authenticated, Bamboo deltes the file with your credentials.
Here’s a list of known issues in this release that might affect you, depending on your environment. Every deployment is unique, so we are listing the issues here to help you make an informed decision about upgrading.
We continue to work on resolving these issues. ETA for some of these fixes can be seen in the “Fix version” column.
Issues resolved in Bamboo 6.3.4Released on .
In this release, we've made changes to our behind-the-firewall analytics plugin to improve the quality and accuracy of the information we collect.
Upgrade your Bamboo instance to version 6.3.4 to get the improvements.
Issues resolved in Bamboo 6.3.3Released on .
Issues resolved in Bamboo 6.3.2Released on .
Issues resolved in Bamboo 6.3.1Released on .
Issues resolved in Bamboo 6.3.0Released on .