From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-sysadm/2011-February/002920.html | 120 ++++++++++++++++++++++++ 1 file changed, 120 insertions(+) create mode 100644 zarb-ml/mageia-sysadm/2011-February/002920.html (limited to 'zarb-ml/mageia-sysadm/2011-February/002920.html') diff --git a/zarb-ml/mageia-sysadm/2011-February/002920.html b/zarb-ml/mageia-sysadm/2011-February/002920.html new file mode 100644 index 000000000..1f2ebfd6f --- /dev/null +++ b/zarb-ml/mageia-sysadm/2011-February/002920.html @@ -0,0 +1,120 @@ + + + + [Mageia-sysadm] svn -> bugzilla hook + + + + + + + + + +

[Mageia-sysadm] svn -> bugzilla hook

+ Ahmad Samir + ahmadsamir3891 at gmail.com +
+ Thu Feb 24 21:29:36 CET 2011 +

+
+ +
On 21 February 2011 23:59, Romain d'Alverny <rdalverny at gmail.com> wrote:
+> On Mon, Feb 21, 2011 at 08:47, Dexter Morgan <dmorganec at gmail.com> wrote:
+>> On Mon, Feb 21, 2011 at 8:09 AM, Michael Scherer <misc at zarb.org> wrote:
+>>> On Mon, 21 Feb 2011 04:16:27 +0200, Ahmad Samir wrote:
+>>>>
+>>>> Are there any plans to add an svn -> bugzilla hook? (like the one
+>>>> that's used in Mandriva).
+>>>>
+>>>> It proved to be useful as it:
+>>>> - gives feedback to the reported
+>>>> - makes is easy for anyone to see which commit is supposed to fix a
+>>>> certain bug
+>>>>
+>>>> No pressure, though, just putting the idea out there for when you have
+>>>> the time to work on it.
+>>>
+>>> If you would gather the list of requirement for us, it will help.
+>>> Ie, what kind of hook would be useful, what syntax does already exist, etc.
+>>
+>> sound a good idea.   Is there a wiki page where we could do this ?
+>
+> You open it. Or Ahmad, he started the thread :-p
+>
+> As for the requirements, I can't speak for Ahmad, but that may start
+> the picture.
+>
+> I used to use Trac with such a Subversion post-commit hook, as documented here:
+> http://trac.edgewall.org/wiki/TracInstall#AutomaticreferencetotheSVNchangesetsinTractickets
+>
+> In short:
+>  - having "fixes #123" or "closes #123" in the commit message would
+> add the comment to ticket #123 + a reference to the commit, and close
+> it;
+>  - having "refs #123" or "see #123" in the commit message would only
+> add the comment + a reference as well.
+>
+> Now, with Bugzilla, that could be a bit more complex:
+>  * should we have a "fixes #123 resolved"? or is it implied?
+>  * we have to make sure that our revision id is understood and
+> correctly rewritten to the right URL
+>  * how to do we make Bugzilla understand that a specific commit
+> revision would map to a given Web URL for direct review? (interpreting
+> correctly whether it comes from a git or a svn scm; or others).
+>
+> Checking https://wiki.mozilla.org/Bugzilla:Addons#Integration_with_Source_Code_Management_programs
+> and then https://wiki.mozilla.org/Bugzilla:Addons#Bugzilla_Extensions
+> there seems to be some tools but I could not see one that fits here
+> exactly.
+>
+
+Sorry for the late reply.
+
+I don't know how the under-the-hood stuff work with respect to this
+issue. What I know is how it was used in mdv, adding:
+CCBUG: #123
+on a separate line.
+
+Or (mdv#123) would post a comment to bugzilla, e.g.:
+
+https://qa.mandriva.com/show_bug.cgi?id=61384#c27
+
+-- 
+Ahmad Samir
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ -- cgit v1.2.1