Connect to an OnDemand Plugins from a BTF JIRA (Could not find a handler capable of installing the add-on)

129 views
Skip to first unread message

Martin Cleaver

unread,
Nov 23, 2013, 12:44:08 PM11/23/13
to atlassian-...@googlegroups.com, Roberto Dominguez
Hi all,

I understand from Roberto that this works for Confluence, so I want to understand whether it should work also for JIRA.

I want to make this downloaded JIRA connect to Connect/OnDemand, so it can use OnDemand plugins.

I have a new JIRA 6.1.3, upgraded to UPM 2.1.4, and then switched it to onOndemand mode (using Add in bin/setenv.sh to JVM_REQUIRED_ARGS, -Datlassian.upm.on.demand=true).

Now it shows:

We want this for a new (private listed) plugin.

- I successfully created a new Token 

In my non-Ondemand JIRA, go to http://<server>:8080/plugins/servlet/upm?upmDeveloper=true#manage and Upload. (I understand from https://groups.google.com/forum/#!topic/atlassian-connect-dev/U0Qu5KLy2ME that this upmDeveloper=true step is no longer necessary)

This fails with:


The logs (after com.atlassian.upm and com.atlassian.marketplace are switched on) say:

2013-11-23 12:22:26,132 UpmAsynchronousTaskManager:thread-4 INFO admin 693x282x1 8zyyz5 69.165.217.125 /rest/plugins/1.0/ [atlassian.upm.impl.PluginDownloadServiceImpl] Downloading plugin artifact from [https://marketplace.atlassian.com/files/artifact/descriptor/bfb-xxxxx-xxxxx/atlassian-plugin.xml?access-token=ac25xxxx]...
2013-11-23 12:22:26,281 UpmAsynchronousTaskManager:thread-4 ERROR admin 693x282x1 8zyyz5 69.165.217.125 /rest/plugins/1.0/ [atlassian.upm.manager.PluginInstaller] Failed to install plugin 'atlassian-plugin.xml': Unable to install plugin - file was not a supported plugin artifact type
2013-11-23 12:22:26,281 UpmAsynchronousTaskManager:thread-4 DEBUG admin 693x282x1 8zyyz5 69.165.217.125 /rest/plugins/1.0/ [atlassian.upm.manager.PluginInstaller] com.atlassian.upm.manager.UnknownPluginTypeException: Unable to install plugin - file was not a supported plugin artifact type
com.atlassian.upm.manager.UnknownPluginTypeException: Unable to install plugin - file was not a supported plugin artifact type
at com.atlassian.upm.manager.PluginInstallationServiceImpl.installPlugin(PluginInstallationServiceImpl.java:118)
at com.atlassian.upm.manager.PluginInstaller.execute(PluginInstaller.java:141)
at com.atlassian.upm.manager.PluginInstaller.install(PluginInstaller.java:96)
at com.atlassian.upm.rest.resources.install.InstallTask.installFromFile(InstallTask.java:121)
at com.atlassian.upm.rest.resources.install.InstallRemotePluginTask.executeTask(InstallRemotePluginTask.java:73)
at com.atlassian.upm.rest.resources.install.InstallTask.call(InstallTask.java:62)
at com.atlassian.upm.rest.resources.install.InstallTask.call(InstallTask.java:32)
at com.atlassian.upm.rest.async.AsynchronousTaskManager$1.call(AsynchronousTaskManager.java:77)
at com.atlassian.upm.rest.async.AsynchronousTaskManager$1.call(AsynchronousTaskManager.java:72)
at com.atlassian.sal.core.executor.ThreadLocalDelegateCallable.call(ThreadLocalDelegateCallable.java:42)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
2013-11-23 12:22:26,324 UpmAsynchronousTaskManager:thread-4 INFO admin 693x282x1 8zyyz5 69.165.217.125 /rest/plugins/1.0/ [atlassian.upm.log.PluginSettingsAuditLogService] Sat Nov 23 12:22:26 EST 2013 admin: Failed to install add-on plugin.xxxxxxx.atlassian-plugin.xml



So I figured to try Atlassian's connect add-on, "Who's Looking for OnDemand". Same:


2013-11-23 12:40:43,234 http-bio-8080-exec-15 INFO admin 760x599x1 bw9yrr 69.165.217.125 /rest/plugins/1.0/available/recent [atlassian.marketplace.client.MarketplaceClient] GET https://marketplace.atlassian.com/rest/1.0/
2013-11-23 12:40:43,236 http-bio-8080-exec-15 INFO admin 760x599x1 bw9yrr 69.165.217.125 /rest/plugins/1.0/available/recent [atlassian.marketplace.client.MarketplaceClient] GET https://marketplace.atlassian.com/rest/1.0/plugins/search?q=looking&onDemand=true&onPremise=false&application=jira&buildNumber=6158&limit=10
2013-11-23 12:40:47,901 UpmAsynchronousTaskManager:thread-3 INFO admin 693x278x1 8zyyz5 69.165.217.125 /rest/plugins/1.0/available/featured [atlassian.upm.impl.PluginDownloadServiceImpl] Downloading plugin artifact from [https://marketplace.atlassian.com/download/plugins/whoslooking-connect/version/150/descriptor]...
2013-11-23 12:40:48,209 UpmAsynchronousTaskManager:thread-3 ERROR admin 693x278x1 8zyyz5 69.165.217.125 /rest/plugins/1.0/available/featured [atlassian.upm.manager.PluginInstaller] Failed to install plugin 'Who's Looking for OnDemand': Unable to install plugin - file was not a supported plugin artifact type
2013-11-23 12:40:48,209 UpmAsynchronousTaskManager:thread-3 DEBUG admin 693x278x1 8zyyz5 69.165.217.125 /rest/plugins/1.0/available/featured [atlassian.upm.manager.PluginInstaller] com.atlassian.upm.manager.UnknownPluginTypeException: Unable to install plugin - file was not a supported plugin artifact type
com.atlassian.upm.manager.UnknownPluginTypeException: Unable to install plugin - file was not a supported plugin artifact type
at com.atlassian.upm.manager.PluginInstallationServiceImpl.installPlugin(PluginInstallationServiceImpl.java:118)
at com.atlassian.upm.manager.PluginInstaller.execute(PluginInstaller.java:141)
at com.atlassian.upm.manager.PluginInstaller.install(PluginInstaller.java:96)
at com.atlassian.upm.rest.resources.install.InstallTask.installFromFile(InstallTask.java:121)
at com.atlassian.upm.rest.resources.install.InstallRemotePluginTask.executeTask(InstallRemotePluginTask.java:73)
at com.atlassian.upm.rest.resources.install.InstallTask.call(InstallTask.java:62)
at com.atlassian.upm.rest.resources.install.InstallTask.call(InstallTask.java:32)
at com.atlassian.upm.rest.async.AsynchronousTaskManager$1.call(AsynchronousTaskManager.java:77)
at com.atlassian.upm.rest.async.AsynchronousTaskManager$1.call(AsynchronousTaskManager.java:72)
at com.atlassian.sal.core.executor.ThreadLocalDelegateCallable.call(ThreadLocalDelegateCallable.java:42)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
2013-11-23 12:40:48,257 UpmAsynchronousTaskManager:thread-3 INFO admin 693x278x1 8zyyz5 69.165.217.125 /rest/plugins/1.0/available/featured [atlassian.upm.log.PluginSettingsAuditLogService] Sat Nov 23 12:40:48 EST 2013 admin: Failed to install add-on plugin.1843997982651220284.atlassian-plugin.xml
2013-11-23 12:40:48,567 http-bio-8080-exec-17 INFO admin 760x608x1 bw9yrr 69.165.217.125 /rest/plugins/1.0/available/whoslooking-connect-key [atlassian.marketplace.client.MarketplaceClient] GET https://marketplace.atlassian.com/rest/1.0/
2013-11-23 12:40:48,568 http-bio-8080-exec-17 INFO admin 760x608x1 bw9yrr 69.165.217.125 /rest/plugins/1.0/available/whoslooking-connect-key [atlassian.marketplace.client.MarketplaceClient] GET https://marketplace.atlassian.com/rest/1.0/plugins/whoslooking-connect?onDemand=true&onPremise=false&application=jira&buildNumber=6158&limit-versions=0&limit-reviews=0
2013-11-23 12:40:48,774 http-bio-8080-exec-17 INFO admin 760x609x1 bw9yrr 69.165.217.125 /rest/plugins/1.0/whoslooking-connect-key/recommendations [atlassian.marketplace.client.MarketplaceClient] GET https://marketplace.atlassian.com/rest/1.0/
2013-11-23 12:40:48,775 http-bio-8080-exec-17 INFO admin 760x609x1 bw9yrr 69.165.217.125 /rest/plugins/1.0/whoslooking-connect-key/recommendations [atlassian.marketplace.client.MarketplaceClient] GET https://marketplace.atlassian.com/rest/1.0/plugins/whoslooking-connect?onDemand=false&onPremise=false&limit-versions=0&limit-reviews=0
2013-11-23 12:40:48,806 http-bio-8080-exec-4 INFO admin 760x610x2 bw9yrr 69.165.217.125 /rest/plugins/1.0/available/whoslooking-connect-key/watch [atlassian.marketplace.client.MarketplaceClient] GET https://marketplace.atlassian.com/rest/1.0/
2013-11-23 12:40:48,807 http-bio-8080-exec-4 INFO admin 760x610x2 bw9yrr 69.165.217.125 /rest/plugins/1.0/available/whoslooking-connect-key/watch [atlassian.marketplace.client.MarketplaceClient] GET https://marketplace.atlassian.com/rest/1.0/notifications/whoslooking-connect?username=enrique.cadalso%40blendedperspectives.com&sen=SEN-L3285624
2013-11-23 12:40:48,823 http-bio-8080-exec-17 INFO admin 760x609x1 bw9yrr 69.165.217.125 /rest/plugins/1.0/whoslooking-connect-key/recommendations [atlassian.marketplace.client.MarketplaceClient] GET https://marketplace.atlassian.com/rest/1.0/plugins/whoslooking-connect/bayesian-recommendations?application=jira&buildNumber=6158


How much of this should work? Are there known steps other than Settings > Enable Private Listings? Did I miss something?

Thanks kindly,
   Martin.


Andy Brook

unread,
Nov 23, 2013, 12:55:56 PM11/23/13
to atlassian-...@googlegroups.com, Roberto Dominguez
I tried this with a local JIRA @ Atalssian Lab week in Amsterdam a couple of days ago, I spent several hours with a working remoted helloworld and a standalone jira with that -Datlassian.upm.on.demand=true setting.  It did not work, and I got the same message. 

It wasn't clear from those present if there is an expectation that it should work (a bug) or that it worked once and isn't expected to work ongoing.  I had to revert to the atlas-run-standalone with the UPM options set to get anything working.  I was shown how to modify the UPM screen url to include ?devMode=true as an argument as well.  But it didn't help.


--
You received this message because you are subscribed to the Google Groups "Atlassian Connect Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to atlassian-connec...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.



--
Andy Brook

PastedGraphic-6.tiff
PastedGraphic-7.tiff
Find new add-ons - JIRA Blended Perspectives Test 2013-11-23 11-38-40.jpg

Peter Brownlow

unread,
Nov 24, 2013, 4:08:34 AM11/24/13
to atlassian-...@googlegroups.com, Roberto Dominguez
Hi all,

There is work currently underway to improve the error message using Andy's feedback from the Connect Lab Week in Amsterdam. That you're unable to install the add-on in this exact situation is legit but the error message needs to be better at saying what the problem is and how to fix it.

The problem: you can't install a Connect add-on without both being in OnDemand mode and having the atlassian-connect plugin installed.

How to fix it: either use an OnDemand instance from Atlassian's OnDemand cloud (because these are all in OnDemand mode and have the atlassian-connect plugin installed) or manually ensure that both OnDemand mode is on and the atlassian-connect plugin is installed. You can install the plugin manually or use the --bundled-plugins arg to atlas-run-standalone as described at <https://developer.atlassian.com/display/AC/Hello+World> under the heading "Starting with the SDK". An existing BTF instance or an existing instance that you have been using for in-process plugin development probably won't have the atlassian-connect plugin installed.

-Peter
To unsubscribe from this group and stop receiving emails from it, send an email to atlassian-connect-dev+unsub...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.



--
Andy Brook

Andy Brook

unread,
Nov 24, 2013, 5:38:43 AM11/24/13
to atlassian-...@googlegroups.com
Hi Peter, yes, that makes sense, thanks for the clarification on how to get standalone working!


To unsubscribe from this group and stop receiving emails from it, send an email to atlassian-connec...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.



--
Andy Brook

Seb Ruiz

unread,
Nov 24, 2013, 6:51:00 AM11/24/13
to atlassian-...@googlegroups.com
To add to Peter's message, you will need more than simply the atlassian-connect plugin installed. There are other dependencies which AC relies on that are also not shipped with standalone JIRA/Confluence.

These deps can be found on the latest release notes for AC, eg at https://developer.atlassian.com/display/AC/2013/11/19/1.0-m21+Release+Notes
Seb Ruiz
Atlassian
Reply all
Reply to author
Forward
0 new messages