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
Date Mon, 12 Nov 2012 10:01:13 GMT

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

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

Thanks for reviewing the script! Running it in the ASF infrastructure would be preferable
because of its reliability and 24/7 supervision. E.g. in September there were problems where
the computer that is currently running the script was hit by a power glitch while I was traveling,
so the automatic updates didn't work for a while, which was a bit confusing for committers
then.

The script and its config need to be adjusted soon though because the SVN path of the Apache
OpenOffice project will move after it graduated [INFRA-5417].

I'd be happy to share the script publicly if bugzilla allowed automated login and updates
only for specific groups (e.g. "allow_RPC_login"), but AFAIK this isn't possible yet in Bugzilla.

The config file must be especially protected because it contains the login details of a bot
user with very high credentials so that it can do its job also in issues with restricted visibility
such as security-problems.
                
> 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

Mime
View raw message