Bamboo 5.5 upgrade notes
We’ve collected some important notes on upgrading to Bamboo 5.5. For details on all the new features and improvements we’ve introduced in this release, see the Bamboo 5.5 release notes .
Upgrade notes
Here’s some important information you should know about before upgrading.
OAuth for application links
We recommend that you add OAuth authentication (in addition to existing authentication) to any existing application links between your Bamboo and Bitbucket servers. If you have previously integrated Bamboo with Bitbucket Server, you will probably have Basic HTTP authentication configured for your link. The new Bitbucket repository type will work with Basic HTTP, but OAuth is better as it is an impersonating authentication type. For more information, see Configuring authentication for an application link.
Upgrade to Git 1.7.1
Git will use --ancestry-path when trying to extract changeset due to BAM-13760 - Too many notifications for release -> feature merge in Git plan branches CLOSED. Since that command is available for Git 1.7.2 and above (see Release Notes), please upgrade your native Git, if you have Git 1.7.1 installed (especially those who use RHEL 6 or CentOS).
Changes to supported platforms
This release of Bamboo does not introduce any changes to supported platforms. For more information about what the latest stable release of Bamboo supports, see Supported platforms.
How to upgrade Bamboo
See the Bamboo upgrade guides for a complete walk-through of the upgrade process that includes descriptions of all the available upgrade paths, prerequisites, and methods.