focbenz
commented
1 year ago We are affected as well during and could only start Bamboo Server 8.2.7 suddenly with the same issue. Raising the log level in Bamboo Serverfor plugins to debug surprisingly helped to work around that race condition. (ignoring the ERRORs in the log when starting.)
The only newer version of Allure Report for Bamboo verion 1.16.1 seems to only have "DC Support" and does not mention any other bug fixes.
So Atlassian basically reminds the creators of the "Allure for Bamboo" / "Allure Report for Bamboo" plugin to v2 update to the Spring scanner library
This knowledge base entry is for Confluence but also goes for Bamboo: https://confluence.atlassian.com/confkb/plugins-failing-to-start-due-to-plugin-has-an-extra-copy-of-atlassian-spring-scanner-annotation-classes-959299076.html
Hi ,
we are using bamboo v 8.2.5 and recently i upgraded Allure for Bamboo from v.1.14.0 to v.1.15.0, all agents are started reporting the below error, now I have downgraded back to v.1.14.0 and agents are running fine
ERROR : Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'executableBuildAgent' defined in class path resource [applicationContextRemoteAgentStartupCore.xml]: Invocation of init method failed; nested exception is com.atlassian.bamboo.exception.StartupException: Mission critical plugins did not start: com.atlassian.bamboo.plugins.atlassian-bamboo-plugin-git:gitv2, com.atlassian.bamboo.plugins.atlassian-bamboo-plugin-bitbucket:bbCloud, com.atlassian.bamboo.plugins.stash.atlassian-bamboo-plugin-stash:bbserver
Caused by: com.atlassian.bamboo.exception.StartupException: Mission critical plugins did not start: com.atlassian.bamboo.plugins.atlassian-bamboo-plugin-git:gitv2, com.atlassian.bamboo.plugins.atlassian-bamboo-plugin-bitbucket:bbCloud, com.atlassian.bamboo.plugins.stash.atlassian-bamboo-plugin-stash:bbserver at com.atlassian.bamboo.utils.startup.PluginSystemStartupUtils.verifyBundledPluginsAvailability(PluginSystemStartupUtils.java:47)