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: [email protected]
For additional commands, e-mail: [email protected]
