new jira-rest-plugin: request for commit access

[Stefan Thurnherr]

Hi all

I'm working on a new jira plugin that will use the rest api available in jira. The existing jira plugin uses the soap/rpc api which will probably be deprecated with JIRA 7 - see https://issues.jenkins-ci.org/browse/JENKINS-18166.

I'm currently working on the new jira-rest-plugin in my personal git repo: https://github.com/stefanthurnherr/jenkins-jira-rest-plugin. Not much to show yet, but soon....

Is it possible to get commit access to https://github.com/jenkinsci so I can create and publish the new plugin? I intend to call the plugin "jira-rest-plugin".

Thanks!
 stefan.

[Slide]

Is there any reason you couldn't add the capability to the existing plugin instead of writing a new plugin?

slide

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
Website: http://earl-of-code.com

[Stefan Thurnherr]

Yeah I considered that. However changing from soap/rpc to rest feels like quite a big change, which I believe makes it justifiable to create a new plugin. Code also becomes more maintainable if it doesn't include any soap stuff.

And the plugin does not persist much information (user/pass, url, query) so it's no big issue to migrate for users.

But please share your thoughts :-)

stefan.

[Slide]

I wouldn't change from SOAP to REST, I would refactor to support both somehow.

slide

[Christoph Kutzinski]

+1 for adding this to the existing plugin.
Probably would make migration to JIRA 7 much less painless for users of the existing plugin

[Daniel Beck]

On 28.03.2014, at 22:48, Stefan Thurnherr <stefan.t...@gmail.com> wrote:

> feels like quite a big change, which I believe makes it justifiable to create a new plugin

If necessary (no additional option 'Use SOAP'/'Use REST' feasible) you could keep as much as possible from the existing plugin, and make this a Jira plugin 2.0 instead.

IIRC there's a way to mark releases as incompatible in update center, so users will be made aware of the big difference before installing.

[Stefan Thurnherr]

@DanielBeck: I like that option as it will allow me to drop the soap-related stuff while still reusing the existing code.

I'd like to migrate to jenkins credentials at the same time and drop the input fields for user/pass. Or maybe there is a recommended way of migrating plugins from user/pass input fields to the credentials plugin?

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/j1gcydeNiUI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.

[Dominik Bartholdi]

+1 on migrating from SOAP to REST in the existing plugin and all +1 on moving to the credentials plugin support.

Rather the doing some hacky username/password converting from the old way to the new, you could also use the AdministrativeMonitor ExtensionPoint to inform the admin about the incomplete migration and what he has to do.

Domi

 

You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.

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