www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Herbert Duerr (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-5004) Automatic updates from Repository into Bugzilla (e.g. using "scmbug")
Date Thu, 05 Jul 2012 20:05:34 GMT

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

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

Since this issue is already drawing attention in the mailing list
http://mail-archives.apache.org/mod_mbox/incubator-ooo-dev/201207.mbox/%3CC9487A84-2969-4330-8CFB-B67F45E0EA41%40comcast.net%3E
I'd like to update the status of this idea: I now wrote a script that parses the commit  message
looking for AOO bug references and if it finds one it updates the bugzilla entry with the
revision id and the commit summary. So the bugzilla side of the automation is almost ready.
I'll have to talk with svn gurus on how to integrate with the svnpubsub client (thanks to
Danie Shahaf for the idea)
                
> Automatic updates from Repository into Bugzilla (e.g. using "scmbug")
> ---------------------------------------------------------------------
>
>                 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message