Bamboo Data Center 13.0 Early Access Program release

We are happy to announce the availability of the new version of Bamboo Data Center 13.0 Early Access Program (EAP) release.

This Early Access Program release enables partners and customers with custom in-house applications to test compatibility and prepare their integrations ahead of Bamboo 13.0’s general availability.

Important things to note about this EAP release:

  • Don’t use this EAP release in production environments. For all Bamboo production, use Bamboo 12.1.x, the latest official release.

  • The general availability release is still underway and may contain some changes. However, this EAP release is intended to contain a complete picture of Bamboo 13.0’s improvements.

Using the EAP

EAP can be downloaded as a zip archive for Windows x64 and a tar.gz archive for Linux. For installation instructions, head to the documentation.

Overview of changes in the EAP

Take a sneak peak of changes that will be available when you upgrade to Bamboo 13.0. You can expect:

  • Platform 9 upgrade for enhanced security, stability, and future-proofing, such as Java 25, Tomcat 11, Spring 7, and more

  • Apache commons-configuration removal

  • Jackson 3 upgrade

  • Removal of support for transformed plugins

  • Zero Downtime Upgrades

and many more. Find out more about what’s changed from the Bamboo 13 EAP release notes.

The Atlassian Bamboo Team

@vdebone We have noticed an issue making our app compatible.

It seems that com.atlassian.user package is not accessible to plugins somehow.

We have this class not found exception when we try to enable.



Caused by: java.lang.IllegalStateException: Failed to introspect Class [org.techtime.bamboo.plugins.easysso.ApplicationInfoServiceImpl] from ClassLoader [org.techtime.bamboo.plugins.easysso [127]]

	at org.springframework.util.ReflectionUtils.getDeclaredMethods(ReflectionUtils.java:483)

	at org.springframework.util.ReflectionUtils.doWithLocalMethods(ReflectionUtils.java:320)

	at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.checkLookupMethods(AutowiredAnnotationBeanPostProcessor.java:460)

	... 49 more

Caused by: java.lang.NoClassDefFoundError: com/atlassian/user/User

	at java.base/java.lang.Class.getDeclaredMethods0(Native Method)

	at java.base/java.lang.Class.privateGetDeclaredMethods(Class.java:3010)

	at java.base/java.lang.Class.getDeclaredMethods(Class.java:2329)

	at org.springframework.util.ReflectionUtils.getDeclaredMethods(ReflectionUtils.java:465)

	... 51 more

Caused by: java.lang.ClassNotFoundException: com.atlassian.user.User not found by org.techtime.bamboo.plugins.easysso [127]

	at org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1591)

	at org.apache.felix.framework.BundleWiringImpl.access$300(BundleWiringImpl.java:79)

	at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1976)

	at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:490)

Our manifest has correctly added the package to our import-package and the system bundle seems to be exporting the package to atlassian plugins.

This has been acknowledged as bug (https://jira.atlassian.com/browse/BAM-26571) and will be fixed in the final release.