You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by Andrew Stitcher <as...@redhat.com> on 2013/01/24 22:04:25 UTC
Jira subversion or git integration
Last July (2012) The Jira subversion integration was disabled.
Speaking personally (and I expect for a good number of members of the
qpid team) I'm finding it much harder to follow jiras into the changes
that relate to them.
Indeed, previously Qpid put in place a policy that led to most Qpid
checkins having a related JIRA isuue number in the checkin log precisely
to enable our tracking.
Is there currently a plan to bring back the subversion integration?
Alternatively I think we would be perfectly happy with an integration
with the git mirror of the repository if that is easier.
If there is no plan to resurrect any source code integration we will
need to find some other way to relate the changes, and it would be good
to know so we can kick off this work.
Thanks
Andrew
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
Re: Jira subversion or git integration
Posted by Herbert Duerr <hd...@apache.org>.
On 24.01.2013 22:04, Andrew Stitcher wrote:
> Last July (2012) The Jira subversion integration was disabled.
>
> Speaking personally (and I expect for a good number of members of the
> qpid team) I'm finding it much harder to follow jiras into the changes
> that relate to them.
>
> Indeed, previously Qpid put in place a policy that led to most Qpid
> checkins having a related JIRA isuue number in the checkin log precisely
> to enable our tracking.
>
> Is there currently a plan to bring back the subversion integration?
> Alternatively I think we would be perfectly happy with an integration
> with the git mirror of the repository if that is easier.
>
> If there is no plan to resurrect any source code integration we will
> need to find some other way to relate the changes, and it would be good
> to know so we can kick off this work.
As Tony mentioned the JIRA plugin was disabled because it didn't scale
good enough for huge SVN repositories.
If you're considering an alternative solution maybe my svn2bz [1] script
could be useful here if someone extended it with the few lines to
support JIRA's REST API [2] for updating issues. The script scales very
well with huge SVN repositories because it doesn't care about them
directly, it only subscribes to their svnpubsub service to listen for
changes.
We're using the svn2bz robot for many months now to update Apache
OpenOffice bugzilla issues when a commit message references them. A
recent example is available at [3].
[1]
https://svn.apache.org/repos/infra/infrastructure/trunk/projects/svn2bz/svn2bz.py
[2]
https://developer.atlassian.com/display/JIRADEV/Updating+an+Issue+via+the+JIRA+REST+APIs
[3] https://issues.apache.org/ooo/show_bug.cgi?id=121421#c35
Herbert
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
Re: Jira subversion or git integration
Posted by Olivier Lamy <ol...@apache.org>.
if you are using Jenkins, you can activate the jira plugin.
This will add comment to your jira entry as this sample:
https://issues.apache.org/jira/browse/MTOMCAT-185?focusedCommentId=13497111&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13497111
note you must add the jira entry key in your comment.
2013/1/25 Andrew Stitcher <as...@redhat.com>:
> On Fri, 2013-01-25 at 07:20 +0000, Tony Stevenson wrote:
>> Andrew,
>>
>> The reason the SVN integration was dropped was because the code that runs that module was extremely inefficient.
>> We submitted a patch to Atlassian, which to my knowledge still has yet to be applied, and until it is we cannot run it as the current code cannot cope with a repo of >=1.4m revs.
>>
>> So until that situation is resolved we will not run that code again, as it was incredibly detrimental to the JIRA service. If someone finds a *good* 3rd party plugin, available via the Atlassian UPM we might consider that. But I have yet to see one.
>
> Thanks for the clear explanation.
>
> Is this also true for git integration? Is there git integration
> available for JIRA (that we could potentially use)?
>
>>
>> There is *nothing* stopping you entering the JIRA issue into the commit log anyway, thats seems like a good practice to me anyway. So when and if the service is ultimately restored it will pick it up anyway.
>
> I was not suggesting that we will stop entering the issue number in the
> commit log at all. Just that we might need some other way to get from
> the JIRA entry to the commit (I'm thinking of an automatic process that
> examines our commit entries and then adds svn urls to the JIRA issues in
> a comment).
>
> Andrew
>
>
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
Re: Jira subversion or git integration
Posted by Marvin Humphrey <ma...@rectangular.com>.
On Fri, Jan 25, 2013 at 6:52 AM, Daniel Gruno <ru...@cord.dk> wrote:
> 4) Use JIRA's REST API to post a comment in the appropriate JIRA ticket.
Will adding to the comment load like this speed the day when the ASF's
gigantic monolithic JIRA instance topples over from sheer size?
(The "JIRApocalypse"?)
Marvin Humphrey
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
Re: Jira subversion or git integration
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Daniel Gruno wrote on Fri, Jan 25, 2013 at 15:52:17 +0100:
> On 01/25/2013 03:40 PM, Andrew Stitcher wrote:
> > On Fri, 2013-01-25 at 07:20 +0000, Tony Stevenson wrote:
> >> Andrew,
> >>
> >> The reason the SVN integration was dropped was because the code that runs that module was extremely inefficient.
> >> We submitted a patch to Atlassian, which to my knowledge still has yet to be applied, and until it is we cannot run it as the current code cannot cope with a repo of >=1.4m revs.
> >>
> >> So until that situation is resolved we will not run that code again, as it was incredibly detrimental to the JIRA service. If someone finds a *good* 3rd party plugin, available via the Atlassian UPM we might consider that. But I have yet to see one.
> >
> > Thanks for the clear explanation.
> >
> > Is this also true for git integration? Is there git integration
> > available for JIRA (that we could potentially use)?
> >
> >>
> There is a way to have git -> jira integration, but it involves some
> steps that you need to clear with infra and your project. Currently, we
> do not have a plugin for git -> jira, but we do have a gitpubsub server,
> which means that you could potentially do the following:
>
> 1) Have a client listen to gitpubsub
> 2) When a log message contains fx. QPID-1234, register that message
> 3) Create a user account for said script in JIRA, and give it comment access
> 4) Use JIRA's REST API to post a comment in the appropriate JIRA ticket.
>
> As said, this would need to be cleared with the respective groups first,
> but it is a possibility.
>
> If you get the a-okay for this, I'd be happy to implement it for you.
>
Presumably as a patch to Herbert's script? {svn,git}2{bz,jira}
> With regards,
> Daniel.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
Re: Jira subversion or git integration
Posted by Daniel Gruno <ru...@cord.dk>.
On 01/25/2013 03:40 PM, Andrew Stitcher wrote:
> On Fri, 2013-01-25 at 07:20 +0000, Tony Stevenson wrote:
>> Andrew,
>>
>> The reason the SVN integration was dropped was because the code that runs that module was extremely inefficient.
>> We submitted a patch to Atlassian, which to my knowledge still has yet to be applied, and until it is we cannot run it as the current code cannot cope with a repo of >=1.4m revs.
>>
>> So until that situation is resolved we will not run that code again, as it was incredibly detrimental to the JIRA service. If someone finds a *good* 3rd party plugin, available via the Atlassian UPM we might consider that. But I have yet to see one.
>
> Thanks for the clear explanation.
>
> Is this also true for git integration? Is there git integration
> available for JIRA (that we could potentially use)?
>
>>
There is a way to have git -> jira integration, but it involves some
steps that you need to clear with infra and your project. Currently, we
do not have a plugin for git -> jira, but we do have a gitpubsub server,
which means that you could potentially do the following:
1) Have a client listen to gitpubsub
2) When a log message contains fx. QPID-1234, register that message
3) Create a user account for said script in JIRA, and give it comment access
4) Use JIRA's REST API to post a comment in the appropriate JIRA ticket.
As said, this would need to be cleared with the respective groups first,
but it is a possibility.
If you get the a-okay for this, I'd be happy to implement it for you.
With regards,
Daniel.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
Re: Jira subversion or git integration
Posted by Andrew Stitcher <as...@redhat.com>.
On Fri, 2013-01-25 at 07:20 +0000, Tony Stevenson wrote:
> Andrew,
>
> The reason the SVN integration was dropped was because the code that runs that module was extremely inefficient.
> We submitted a patch to Atlassian, which to my knowledge still has yet to be applied, and until it is we cannot run it as the current code cannot cope with a repo of >=1.4m revs.
>
> So until that situation is resolved we will not run that code again, as it was incredibly detrimental to the JIRA service. If someone finds a *good* 3rd party plugin, available via the Atlassian UPM we might consider that. But I have yet to see one.
Thanks for the clear explanation.
Is this also true for git integration? Is there git integration
available for JIRA (that we could potentially use)?
>
> There is *nothing* stopping you entering the JIRA issue into the commit log anyway, thats seems like a good practice to me anyway. So when and if the service is ultimately restored it will pick it up anyway.
I was not suggesting that we will stop entering the issue number in the
commit log at all. Just that we might need some other way to get from
the JIRA entry to the commit (I'm thinking of an automatic process that
examines our commit entries and then adds svn urls to the JIRA issues in
a comment).
Andrew
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
Re: Jira subversion or git integration
Posted by Tony Stevenson <pc...@apache.org>.
Andrew,
The reason the SVN integration was dropped was because the code that runs that module was extremely inefficient.
We submitted a patch to Atlassian, which to my knowledge still has yet to be applied, and until it is we cannot run it as the current code cannot cope with a repo of >=1.4m revs.
So until that situation is resolved we will not run that code again, as it was incredibly detrimental to the JIRA service. If someone finds a *good* 3rd party plugin, available via the Atlassian UPM we might consider that. But I have yet to see one.
There is *nothing* stopping you entering the JIRA issue into the commit log anyway, thats seems like a good practice to me anyway. So when and if the service is ultimately restored it will pick it up anyway.
Regards,
Tony
On 24 Jan 2013, at 21:04, Andrew Stitcher <as...@redhat.com> wrote:
> Last July (2012) The Jira subversion integration was disabled.
>
> Speaking personally (and I expect for a good number of members of the
> qpid team) I'm finding it much harder to follow jiras into the changes
> that relate to them.
>
> Indeed, previously Qpid put in place a policy that led to most Qpid
> checkins having a related JIRA isuue number in the checkin log precisely
> to enable our tracking.
>
> Is there currently a plan to bring back the subversion integration?
> Alternatively I think we would be perfectly happy with an integration
> with the git mirror of the repository if that is easier.
>
> If there is no plan to resurrect any source code integration we will
> need to find some other way to relate the changes, and it would be good
> to know so we can kick off this work.
>
> Thanks
>
> Andrew
>
>
Cheers,
Tony
----------------------------------
Tony Stevenson
tony@pc-tony.com
pctony@apache.org
http://www.pc-tony.com
GPG - 1024D/51047D66
----------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org