You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Herbert Duerr (JIRA)" <ji...@apache.org> on 2012/09/05 11:50:07 UTC

[jira] [Commented] (INFRA-5004) Automatic updates from Repository into Bugzilla

    [ https://issues.apache.org/jira/browse/INFRA-5004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13448604#comment-13448604 ] 

Herbert Duerr commented on INFRA-5004:
--------------------------------------

The script is not yet in SVN. The best place to put it would be IMHO next to svnwcsub.py in the subversion directory tools/server-side/svnpubsub/ where I don't have commit rights.

There are some open issues on the script, the most important being that by the time it gets to work on a commit the lineend chars are lost so the script cannot reliably figure out the subject line of the commit. It works around that by taking the first N chars of the commit message.

Sorry for the late response. Due to travel I'll have to delay the cleanup and checking in of the script until october. The local svnbot here will continue to work until the service has been migrated to infra.
                
> Automatic updates from Repository into Bugzilla
> -----------------------------------------------
>
>                 Key: INFRA-5004
>                 URL: https://issues.apache.org/jira/browse/INFRA-5004
>             Project: Infrastructure
>          Issue Type: Wish
>      Security Level: public(Regular issues) 
>          Components: Bugzilla, Subversion
>            Reporter: Herbert Duerr
>            Priority: Minor
>
> Having change management automation where code commits trigger updates of their corresponding bugzilla entries would be very helpful.
> There seem to be several open-source tools available for this, one of the most prominent ones for SVN-Bugzilla integration seems to be SCMBUG (http://www.mkgnu.net/scmbug).
> In the case of Apache OpenOffice there is the convention to mention e.g. "#i123456#" in the commit message summary to indicate that a particular change was done for solving issue number 123456. If the revision number of the commit was used to add a comment to that issue with e.g. "Revision 11223344 committed" and eventually the commit message summary then this would be extremely helpful.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira