Thanks a bunch for your help. I was able to figure out what I was doing wrong. For your future reference, let me explain my setup.
I have WinXP Pro, SVN 1.4.3, Bugzilla 2.22.2, WebSVN 2.1, TortoiseSVN 1.4.3and Scmbug 0_19_7. I have been following instructions found at blog.platinumsolutions.com to a) get SVN and WebSVN to use the same usernames/passwords b) integrate Subversion and Bugzilla using BugTraq and Scmbug. In looking at the log output you suggested, I noticed that my "Issue: #, #, #" was put at the beginning of the log, whereas my regex's were looking for it at the end. This was because I had set bugtraq:append = false. I set it to true and the string was put at the end like it is supposed to be. Something else I noticed was that during installation of the glue, I wasn't able to use a product name with spaces. I later changed the product name in bugzilla to have underscores, but I'm wondering whether I could have simply changed the conf file. Lessons learned: 1) make sure the log output matches what your regex's expect. 2) if using TortoiseSVN (or other BugTraq source), set your properties to also match your regex's 3) during install, you can't have a product name with spaces The cool part about this setup is that in WebSVN, if you view the log, the issue number in the log message becomes a link to that bug in Bugzilla. Thanks again. If you'd like any more info from me, let me know. On 2/9/07, Kristis Makris <[EMAIL PROTECTED]> wrote:
Hi Ryan, On Thu, 2007-02-08 at 21:54 -0800, Ryan Constantine wrote: > Thanks for the quick response. I saw the example you gave: > > bug 441:Improved the documentation of policy log_template by adding > an example log message. > > What I am now confused about is that in my comment dialog box (using > TortoiseSVN), I actually have a separate text box to put the bug id in > - which I did, and which should mean I don't have to put the "bug > 441:" into my comment text. But it doesn't work. I setup bugtraq > properties for the relevant folders. One of these properties, > "bugtraq: comment", activates the text box I just mentioned. As the > argument for bugtraq: comment, I have "Issue: %BUGID%". So naturally, > I've replaced the regex in the conf file. I put ".*Issue:\s*(.*?)$" > for bugid_regex. I also changed the other two. Did I screw this up? > Regular expressions aren't my strong suit. I'm not quite sure how TortoiseSVN enforces the bugtraq properties. I've read their instructions on how to set them up, but it seems that these properties are not always applied -- e.g. they are not applied on new directories. We've had a huge discussion about this issue. My gut feeling is that either the bugtraq properties are not doing their job correctly in this instance or you have a regex error. A dirty way of really seeing what gets produced as the log message is to edit /path/to/repository/hooks/lib/product/Glue/Scm.pm:prepare_final_log_message and insert the following somewhere before all those if statements: open OUTFILE, "> C://output.txt"; print OUTFILE Dumper( $self->activity() ); close OUTFILE; This should printout, after you attempt to commit, the data activity structures. You should be able to see the "original_log_message" as constructed by TortoiseSVN, and hopefully debug the problem from there. > Could my problem actually be related to the fact that upon > installation there wasn't an entry made into my bugzilla database? I > had specified --bug=3 (it's a new bugzilla install) when I ran glue > setup, but bugzilla still only shows 2 bugs. Also, the numbered folder > inside the Temp directory remained empty during the installation. From > the installation prompts, I thought there was supposed to be something > there at some point. It just so happens that the numbered folder in the Temp directory remains empty for Subversion -- it contains files for a CVS installation. Also it also happens that currently the "--bug" during installation is not used. Thus I doubt this is an installation problem. The glue is executed correctly. > If I can get this working, I would be happy to write this up my > procedure for inclusion in your manual - or whatever. I would imagine > that I'm not the first person to be a little foggy on the installation > procedure. I'm really curious why this doesn't work. > Thanks again. I look forward to using this tool. > > On 2/8/07, Kristis Makris <[EMAIL PROTECTED] > wrote: > Hi Ryan. > > You installed Scmbug correctly. You simply need to commit with > a log > message in a format similar to: > > http://files.mkgnu.net/files/scmbug/SCMBUG_RELEASE_0-19-7/manual/html-single/manual.html#FIG-LOG-TEMPLATE-EXAMPLE > > > On Thu, 2007-02-08 at 20:09 -0800, Ryan Constantine wrote: > > Error: ** Scmbug error 5: The list of ids supplied was in an > invalid > > format. Only numerical ids are accepted. > > You essentially did not provide a bug id. > > > I also have a general installation question: what dies > installation do > > besides copy some files into the hooks directory of my > repository and > > set up a glue.conf file? > > That's it. > > > For uninstallation, do I simply delete this hooks directory? > > No. The hooks directory contains a post-commit and pre-commit > hook files > that call the glue. You should edit those files and manually > comment out > the calls to the glue. But I can't suggest to you to "simply > delete this > hooks directory" because you might have other hooks in there. > Plus a > hooks directory missing may have special significance to > Subversion > (e.g. it may stop working because "hooks" is missing -- I just > don't > know). > > A similar way to almost uninstall is to edit glue.conf and > disable the > glue. > > I hope this helps. > > > > > -- > Ryan Constantine
-- Ryan Constantine
_______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
