Issue #2 resolved
Radosław Antoniuk
created an issue

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)

  1. Radosław Antoniuk reporter

    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( at com.atlassian.plugin.impl.AbstractPlugin.enable( at com.atlassian.plugin.manager.PluginEnabler.actualEnable( at com.atlassian.plugin.manager.PluginEnabler.enable( at com.atlassian.plugin.manager.DefaultPluginManager.addPlugins( at com.atlassian.plugin.manager.DefaultPluginManager.init( at com.atlassian.bamboo.container.BambooContainer.init( at com.atlassian.bamboo.container.BambooContainer.initialise( at com.atlassian.bamboo.upgrade.UpgradeLauncher.initialiseBambooContainer( at com.atlassian.bamboo.upgrade.UpgradeLauncher.upgradeAndStartBamboo( at com.atlassian.bamboo.upgrade.UpgradeLauncher.contextInitialized( at org.apache.catalina.core.StandardContext.listenerStart( at org.apache.catalina.core.StandardContext.startInternal( at org.apache.catalina.util.LifecycleBase.start( at org.apache.catalina.core.ContainerBase$ at org.apache.catalina.core.ContainerBase$ at at java.util.concurrent.ThreadPoolExecutor.runWorker( at java.util.concurrent.ThreadPoolExecutor$ at 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( at org.apache.felix.framework.Felix.startBundle( at org.apache.felix.framework.BundleImpl.start( at org.apache.felix.framework.BundleImpl.start( at com.atlassian.plugin.osgi.factory.OsgiPlugin.enableInternal( ... 19 more {code}

  2. Radosław Antoniuk 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?

  3. Chandler Zhang

    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.

  4. Chandler Zhang

    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.

  5. Chandler Zhang

    I have

    1. 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
    2. 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.
  6. Radosław Antoniuk 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..:)

  7. Log in to comment