Plugin doesn't start in Bamboo 5.6.2
Plugin version : 5.0.13
Add on gets installed but no plugins (0 out of 6) are enabled. Trying to turn them on results in:
2014-12-03 04:46:23,440 ERROR [ajp-bio-8009-exec-345] [ThrowableExceptionMapper] Uncaught exception thrown by REST service: null java.lang.NullPointerException
Comments (15)
-
Account Deactivated reporter -
I am encountering the same problem on Bamboo 5.7.2 with version 5.0.13.
-
Having same issue with fresh install of 5.7.2.
-
Same again with bamboo 5.7.2
-
I also have the same issue with 5.7.2
-
Was able to fix this locally and submit PR https://bitbucket.org/atlassian/agent-smith-wallboard-plugin/pull-request/24/fixes-issue-2-failure-to-install-plugin
Issue is dependency of new modules on a private graphite plugin. Since this cant be found by the plugin installer it fails. Removing grahite integration from atlassian-plugin.xml, pom and related classes in src/main allows the remaining 4 modules to start without issue.
-
As @eddiewebb said, it is because Agent Smith plugin depends on the graphite-connector-plugin, we have open sourced the plugin and install graphite plugin then install or re-enable agent smith should work.
-
Account Deactivated reporter Hmmm, does the Atlassian SDK provide any plugin dependency management? I mean, shouldn't the plugin decline to install unless graphite-connector-plugin is installed beforehand? Otherwise, I think using graphite is optional with regards to the basic role of this plugin (as the graphite plugin is not available via UPM). What do you think?
-
Currently Agent-Smith is coupled with Graphite plugin. I am not sure if Atlassian SDK can decline the install. However I can publish the graphite plugin to Marketplace to make users' life easier.
-
Account Deactivated reporter That would be definitely useful if you do that! Thanks in advance!
-
I actually find another solution which I think is better. I can decouple the dependency between agent smith and graphite plugin (Well, sort of). After this pr is merged, agent smith does not require graphite any more.
-
I have
- released a new version agent smith (6.0.0) to make the dependency to graphite connector plugin optional. The new version requires bamboo to run on jdk 8
- uploaded the graphite plugin to marketplace, and it is pending approval. If your bamboo is not on jdk 1.8 you should install graphite connector plugin before agent smith.
-
Account Deactivated reporter Thanks for that. I can confirm that it installs now fine, all plugins are enabled, with Bamboo 5.9.4. Here comes a stupid question, how do I access it? The plugin installed fine, but I cannot see any new option anywhere (in the obvious places..:)
-
You can view your bamboo agent and job status through
https://your_bamboo_base_url//viewAgentWallboard.action
-
Account Deactivated reporter - changed status to resolved
Thanks! I think it would be nice to add it in the Wallboard button dropdown, but indeed it works. Thanks for the split!
- Log in to comment
Some more logs: {code} 2014-12-04 00:35:09,036 WARN [localhost-startStop-1] [OsgiPlugin] Because of this exception com.atlassian.plugin.osgi.container.OsgiContainerException: Cannot start plugin: com.atlassian.bamboo.plugin.agent-smith-wallboard at com.atlassian.plugin.osgi.factory.OsgiPlugin.enableInternal(OsgiPlugin.java:483) at com.atlassian.plugin.impl.AbstractPlugin.enable(AbstractPlugin.java:273) at com.atlassian.plugin.manager.PluginEnabler.actualEnable(PluginEnabler.java:116) at com.atlassian.plugin.manager.PluginEnabler.enable(PluginEnabler.java:101) at com.atlassian.plugin.manager.DefaultPluginManager.addPlugins(DefaultPluginManager.java:900) at com.atlassian.plugin.manager.DefaultPluginManager.init(DefaultPluginManager.java:291) at com.atlassian.bamboo.container.BambooContainer.init(BambooContainer.java:177) at com.atlassian.bamboo.container.BambooContainer.initialise(BambooContainer.java:160) at com.atlassian.bamboo.upgrade.UpgradeLauncher.initialiseBambooContainer(UpgradeLauncher.java:188) at com.atlassian.bamboo.upgrade.UpgradeLauncher.upgradeAndStartBamboo(UpgradeLauncher.java:93) at com.atlassian.bamboo.upgrade.UpgradeLauncher.contextInitialized(UpgradeLauncher.java:39) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4887) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5381) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559) at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Caused by: org.osgi.framework.BundleException: Unresolved constraint in bundle com.atlassian.bamboo.plugin.agent-smith-wallboard [29]: Unable to resolve 29.0: missing requirement [29.0] package; (package=com.atlassian.bamboo.plugin.graphiteconnector) at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3409) at org.apache.felix.framework.Felix.startBundle(Felix.java:1709) at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:905) at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:892) at com.atlassian.plugin.osgi.factory.OsgiPlugin.enableInternal(OsgiPlugin.java:459) ... 19 more