+1 for adding this to the existing plugin.
Probably would make migration to JIRA 7 much less painless for users of
the existing plugin
Am 28.03.2014 22:42, schrieb Slide:
Is there any reason you couldn't add the capability to the existing
plugin instead of writing a new plugin?
slide
On Fri, Mar 28, 2014 at 2:37 PM, Stefan Thurnherr
<[email protected] <mailto:[email protected]>> wrote:
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.
--
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 [email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
Website: http://earl-of-code.com
--
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 [email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
