Plugin Exchange: registration, plugins management.

[Vladimir Zenkevich]

Hello Experts,

I have some questions. Could you help me please? My company is developing an opensource JIRA plugin.

1. We would like to place our plugin in 'Plugin Exchange' for internal testing of upgrade possibility via Universal Plugin Manager, so that other users have no access to the plugin (there is no possibility to download our plugin), but we have access to it. We don't understand how to do this. Is it possible? If yes could you please explain how to do this.

2. To create a plugin we need to register vendor. We found in FAQ a similar question (https://developer.atlassian.com/pages/viewpage.action?pageId=6292047), where it is said that it is possible to associate a new account with existing vendor. According to this page we have registered the account (e.g. Account_A) and this account belongs to vendor 'Vendor'. We have other account (e.g. Account_B), but we don't understand how ' Account_A' can associate ' Account_B' with 'Vendor' vendor. We would really appreciate if someone can provide some guide how to do this.

3. How can we edit vendor information?

4. During plugin registration we have to fill some fields like 'screenshots', links to the Jira and Wiki. Is it possible to get access to Atlassian Jira and Wiki, like in the case of this plugin https://plugins.atlassian.com/plugin/details/5150?versionId=35505, https://studio.plugins.atlassian.com/browse/JLINK and create our own documentation on Atlassian Jira and Wiki?

5. As our plugin is opensource we need to make publicly available source code. Is it possible to keep our source code in Atlassian repository? If yes how can we get access to it?


Thanks a lot for any information.

[Vladimir Zenkevich · Accepted solution]

Solved:

Answers received from Atlassian support.

Jonathan Nolen, Jan-09 14:02 (PST):

1. Unfortunately, no. Once you put the plugin on Plugins.atlassian.com, any atlassian customer can download it.
2. You can do so here: https://plugins.atlassian.com/manage/vendor/$My_Vendor_ID$. Just add the other users' email addresses in the bottom right.
3. Same as #2. Look for the "Manager Vendor" link on your vendor page when logged in.
4. We're actually phasing out that service, in favor of Bitbucket.
5. These days, we would strongly encourage you to use Atlassian's code hosting site -- http://bitbucket.org

[JamieA]

I'll have a stab at a couple of those...

1. You don't actually need the plugin in PAC to do this testing... when it's downloaded from PAC it's exactly the same as if you do "install" from the SDK, or upload from file or URL. AFAIK nothing different is happening when it's used by users, it's just that the PAC host is hard-coded.

4. If you fill out the plugin registration forms, in a few days they will approve the plugin, and at this time make you a confluence space. Then you can put your collateral there and link to it from PAC.

5. I believe they will give you a piece of a subversion repo to upload your code, but IMHO you'd be much better of just creating a new repo on bitbucket.

hth, jamie