Bamboo Data Center 10.0 (rc5) Early Access Program release

Bamboo Development
, ,
21

Hi,

I can confirm that fixing seraph-config.xml solved the issue.

Kind Regards,
Jörg

2 Likes
22

@vdebone any updates to share about the WebPanel issue my colleague found?
Thanks in advance.

23

The same issue happens with the release build 10.0.0 build 100006 of Bamboo.
Is this an expected issue and is there another way to get information about the cluster nodes?

1 Like
24

Hi, @JrgBrandsttt why do you need access to that interface? It’s Crowd’s code with dumb implementation at Bamboo side. If you need access to the list of Bamboo nodes you should look at com.atlassian.bamboo.beehive.BambooClusterNodeHeartbeatService interface

25

Just in case anybody missed it:
https://confluence.atlassian.com/bambooreleases/bamboo-10-0-release-notes-1426032299.html
https://confluence.atlassian.com/display/BAMBOORELEASES/Bamboo+10.0+upgrade+notes

26

Ok, with the release 10.0.0 the ‘WebPanel’ conflict sticks in place, as mentioned here.
So, the basic issue is:

Bamboo < 9.6: The interface is: com.atlassian.plugin.web.model.WebPanel
Bamboo 9.6: The interface com.atlassian.plugin.web.model.WebPanel is deprecated in favor of com.atlassian.plugin.web.api.model.WebPanel.
Bamboo 10: The deprecated interface com.atlassian.plugin.web.model.WebPanel is still there. However: I it not exported! At runtime you get a class not found exception:

Caused by: java.lang.ClassNotFoundException: com.atlassian.plugin.web.model.WebPanel not found by ch.mibex.bamboo.sonar4bamboo [128]
        at org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1591) ~[org.apache.felix.framework-7.0.5.jar:?]
        at org.apache.felix.framework.BundleWiringImpl.access$300(BundleWiringImpl.java:79) ~[org.apache.felix.framework-7.0.5.jar:?]
        at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1976) ~[org.apache.felix.framework-7.0.5.jar:?]
        at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:525) ~[?:?]
        ... 140 more

This leaves us with 2 options:

  • Require Bamboo 9.6 and drop support for older Bamboo versions including LTS
  • Find a work around:
    • Is there a way to provide the ‘webpanel’ instance at runtime? Via some Spring Bean, Factory or something else?
    • Ship two different jars: That is probably something we won’t do. Its to much of a hassle.

Any idea or work around is welcome.

1 Like
27

Another thing. The AMPS version of Bamboo 10.0.0 seems broken.

I run a standalone version, and pop-ups to select things like binaries / paths break.

Running it like this:

atlas-run-standalone --product bamboo --version 10.0.0 --data-version 10.0.0 --jvmargs '-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:5007' --container tomcat9x

Once running, I try to specify a Maven home. But the pop-up isn’t handled correctly and shows the top level Bamboo instance:

image
image1466×1237 161 KB

1 Like
28

@vdebone - we expected this to be fixed for GA, but Bamboo 10.0.0 still exhibits this regression (similar to some others discussed in this thread it seems). Is there an ETA for a fix, and are there public issues we can follow and reference when interacting with affected customers?

2 Likes
29

Hi,
The issue with resource caches not being correctly invalidated will be fixed in 10.0.1, soon to be released.

1 Like