Bamboo 9.0 EAP

EAP releases

On this page

Related content

  • No related content found

Still need help?

The Atlassian Community is here for you.

Ask the community

This documentation is intended for third-party app vendors and people maintaining their own in-house apps who want to ensure that the apps are compatible with Bamboo 9.0. If you’d like to stay in the loop, check out the latest posts and discussions in the Atlassian Developer Community. 

Quick info

Here’s some quick information latest early access program (EAP) release:

ApplicationReleaseDownloads
Bamboo Server and Data Center
9.0.0-rc1

 

Download the EAP

Skip to

Summary of the changes

This is an overview of the changes that are going to become part of the upcoming release of Bamboo, so you can start thinking about how they might impact your apps.

Enterprise Data Center Platform upgrade

Status: IMPLEMENTED (EAP01)

We built Bamboo 9.0 on top of Atlassian Platform 6.0, which introduces several significant changes that you should be aware of to verify the compatibility of the apps you’ve built before upgrading Bamboo.

Upgraded third-party libraries

We’ve upgraded the following third-party libraries for compatibility with Atlassian Platform 6.0:

  • jdom was upgraded to 2.0.6.1

  • guava was upgraded to 31.0.1-jre

  • json was upgraded to 20220320

  • rome was upgraded to 1.18.0

Upgraded platform components

We’ve upgraded the following components for compatibility with Atlassian Platform 6.0:

  • parent-poms was upgraded to 6.0.6

  • application-links was upgraded to 9.0.5

  • amps was upgraded to 8.4.2

  • atlassian-activeobjects was upgraded to 4.0.4

  • atlassian-annotations was upgraded to 4.0.0

  • atlassian-cache was upgraded to 6.0.1

  • atlassian-core was upgraded to 8.0.0

  • atlassian-event was upgraded to 5.0.1

  • atlassian-failure-cache was upgraded to 3.0.0

  • atlassian-gadgets was upgraded to 8.0.4

  • atlassian-healthcheck 1 was upgraded to 7.0.0

  • atlassian-httpclient was upgraded to 3.0.0

  • atlassian-oauth was upgraded to 5.0.2

  • atlassian-plugins was upgraded to 7.0.4

  • atlassian-plugins-webfragment was upgraded to 6.0.0

  • atlassian-plugins-webresource was upgraded to 6.0.3

  • atlassian-pretty-urls was upgraded to 4.0.1

  • atlassian-rest was upgraded to 7.0.1

  • atlassian-sal was upgraded to 5.0.0

  • atlassian-scheduler was upgraded to 4.0.0

  • atlassian-soy-templates was upgraded to 6.0.4

  • atlassian-spring-scanner was upgraded to 3.0.1

  • atlassian-template-renderer was upgraded to 5.0.2

  • atlassian-trusted-apps was upgraded to 6.0.0

  • atlassian-vcache was upgraded to 2.0.0

  • beehive was upgraded to 5.0.0

  • caesium was upgraded to 3.1.2

  • io.atlassian.fugue was upgraded to 5.0.0

  • upm-server was upgraded to 6.0.4

Atlassian User Interface (AUI) upgrade

Status: IMPLEMENTED (EAP01)

Bamboo 9.0 updates AUI from 7.10 to 9.4. If your app uses any AUI resources or depends on libraries previously provided by AUI, here’s what you should know:

Because of the AUI upgrade, you might encounter some problems with your apps. See the following sections for more information on the most common issues and ways to fix them:

Issues with dependencies...

Issues with dependencies

Multiple web resources have been removed from the AUI library and are no longer shipped. Additionally, some web-resource key names were changed. See the Web-resource changes section in the AUI upgrade guide for a complete list of changes in the AUI web resources.

If you encounter errors like the following one, you may need to update your app’s dependencies:

Uncaught TypeError: (...) is not a function

If you still encounter such errors after updating your dependencies, then consider checking the order of resources in the <web-resource> section in your atlassian-plugin.xml file. Importing dependencies in the wrong order might also cause such errors.

jQuery UI is no longer bundled in AUI...

jQuery UI is no longer bundled in AUI

jQuery UI's interface components are no longer bundled with AUI. If your app depends on them, you need to either use the equivalent AUI component or import the specific jQuery UI components yourself.

If you decide to ship jQuery UI yourself, make sure that the library is shipped as an AMD module. Otherwise, your library might conflict with internal Bamboo dependencies.

Issues related to Backbone.js...

Issues related to Backbone.js

Backbone.js has been upgraded from version 1.0.0. to version 1.4.0. For more information, see the changelog. If your app relies on the version of Backbone.js shipped with Bamboo, you might encounter issues caused by changes in the library, such as:

  • Backbone no longer automatically attaches options passed to the constructor as this.options.
  • Backbone Models no longer attach url and urlRoot to options.
  • The order of initialization and registering events has changed. In particular, this means that you can no longer set collections in the initialize method and should either use the preinitialize method to set them or pass them directly in a constructor.
Changes to AUI .hidden class behavior...

Changes to AUI .hidden class behavior

In accordance to the AUI documentation, the .hidden class shouldn’t be mixed with jQuery show() and hide() methods. From now, mixing the .hidden class with those methods won't work anymore. Instead, you can do one of the following things:

  • toggle the .hidden class to show or hide the element
  • use the jQuery hide() method to hide the element and then use the show() method to reveal it
Accessing AUI elements in Webdriver tests...

Accessing AUI elements in Webdriver tests

Multiple HTML elements, like checkboxes or form fields, now require special handling in Webdriver tests. Use the com.atlassian.aui:aui-pageobjects dependency and classes from it to interact with the AUI elements inside Webdriver tests. For example:

import com.atlassian.aui.auipageobjects.AuiCheckbox;
...
@ElementBy(id = "createUser_enabled")
private AuiCheckbox userActive;
JavaScript Console warnings...

JavaScript Console warnings

The JavaScript console may throw multiple warnings. For example:

Use of `window.Backbone` through AUI is deprecated and will be removed in AUI 10.0.0
DEPRECATED JS - AJS.template has been deprecated since 8.0.0 and will be removed in 10.0.0. We recommend use of other open-source templating engines, such as "lit-html" or "react". If you cannot do without this templating function, it is available as its own Node package: "@atlassian/aui-template".
DEPRECATED JS - Inline dialog constructor has been deprecated and will be removed in a future release. Use inline dialog 2 instead.

Those warnings come from Bamboo and can be safely ignored.


Artifacts now support multiple copy patterns and exclusion patterns

Status: IMPLEMENTED (EAP01)

Bamboo 9.0 supports adding multiple copy and exclusion patterns to artifact definitions.

This is a breaking change. If your apps use artifacts, make sure to adapt them accordingly (especially those that use the data provided by the Artifact downloader task).


Embedded Crowd upgrade

Status: IMPLEMENTED (EAP01)

Bamboo 9.0 ships with Embedded Crowd 5.0. To find out what’s new in this Crowd release, head over to the Crowd 5.0 release notes.

Tomcat upgrade

Status: IMPLEMENTED (EAP01)

We’ve upgraded Apache Tomcat to version 9.0.64. See the changelog.

Log4j upgrade

Status: IMPLEMENTED (EAP01)

We’ve upgraded Log4j to version 2.17.2. See the changelog.

If you’re using a custom Log4j 1.x configuration with your Bamboo instance, you’ll need to manually migrate it to the Log4j 2.x configuration file format. See Migrating custom logging configurations to Log4j 2.

Changes to supported platforms

See what changes are in store for the supported platforms in Bamboo. For more information about what the latest stable release of Bamboo supports, see Supported platforms.

End-of-support announcements

In this release, we’re deprecating PostgreSQL 10. Because that version of PostgreSQL is going to reach end-of-life in November 2022, we’re planning to remove support for it in a future release of Bamboo.

New supported platforms

Bamboo 9.0 doesn’t introduce support for any new software platforms.

Known issues

There aren’t any known issues to report yet, but we’re keeping an eye out.

Last modified on Dec 22, 2022

Was this helpful?

Yes
No
Provide feedback about this article

Related content

  • No related content found
Powered by Confluence and Scroll Viewport.