We’re preparing for our Bamboo 7.0 release, which will bring a number of breaking changes. To make sure our app vendors and customers who have written in-house apps are prepared for that release, we’re launching the second Bamboo 7.0 Early Access Program (EAP). This is the final one, including divergent branches.
Your feedback is of great value!
Please share any feedback or questions you might have by commenting under this post and our developer team will get back to you.
Important things to note about second EAP release
- This release includes Atlassian Platform 5 upgrade.
- This release should not be used in a production environment.
- This release includes new feature: divergent branches.
Installing the Bamboo 7.0 EAP 2 release
Summary of changes
In this section we’re summing up changes we intend to make in Bamboo 7.0, so you can start thinking how it might impact your apps.
Bamboo 7.0 will allow for branch divergence. You’ll be able to introduce different configurations on different branches in your Bamboo Specs regardless of the master branch configuration. For now, Bamboo will allow branch divergence for Bamboo Specs stored only in Bitbucket Server.
Changes to what Bamboo supports
- Introduce support for Oracle 19
- Introduce support for MsSQL2017
- Drop support for Oracle 12R1
- Drop support for PostgreSQL 9.2, 9.3, 9.4
- Deprecate PostgreSQL 9.5
- Deprecate MSSql2012, MSSql2014
- Deprecate CVS
- Deprecate JGit 7.0
- Deprecate Jenkins importer (Bamboo internal plugin)
As part of our Platform 5 upgrade, we have upgraded Spring framework to 5.1.8. The main difference that can affect plugins is a change to the default Spring autowiring behaviour from “autodetect” to “constructor”. Apps developers should start to use “constructor” injections.