Bamboo 6.3 EAP release notes
We are proud to present Bamboo 6.3 EAP . This release is part of our Early Access Program (EAP) leading up to the official Bamboo 6.3 release. We are making these EAP milestones publicly available so that developers can start assessing the impact of the changes that we are making.
Development releases are snapshots of the ongoing Bamboo development process. For that reason:
- While we try to keep these releases stable, they have not undergone the same degree of testing as a full release.
- Features in development releases may be incomplete, or may change or be removed before the next full release.
Much as you are able to upgrade previous versions of Bamboo to the 6.3 EAP version, and smoothly upgrade from the 6.3 EAP to the final version, once it's released, we don't recommend installing the EAP release on your current production environment. For information about the supported upgrade paths, see Bamboo upgrade guide.
Atlassian does not provide support for development releases.
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.
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 or 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 make your life easier, we've also added a quick overview of repositories and branches used in the plan - the '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.