2006-12-16 12:08:05

Comparison for /Integration Mantis Subversion of 2006-12-16 12:08:05 and 2006-12-16 12:43:36

Additions:

� Joint Education Meeting
Do you want to know how to integrate Mantis and SVN? I did, but could never manage the right Google query to return a page written for someone unfamiliar with customizing Mantis. (I�m still learning SVN too.) This is the documentation I wish I�d had. This process is easier if you know Bash or some other scripting language. This was accomplished using Mantis 1.0.0rc2. An older version may not work with these instructions.

Revision properties such as log messages aren�t versioned. If you were to go back and change a log message, for example, the old one would be lost. This hook, and its post- counterpart, offer a chance to reject or log the change.

Well, that sounds simple. All we have to do is write a script that will log into our bug tracking system and insert a comment on the appropriate ticket. That sounds easy enough, but let�s not make things too complicated. With a few minor customizations, Mantis will do most of the work for us.
The manual for Mantis has two relevant pages. One, titled �Source Control Integration�, provides a list of customizable settings, but offers no directions on where these settings are most appropriately accessed. The other, �CVS integration�, is not terribly helpful either, but it does provide another piece of our puzzle�it tells us there is a command line PHP script included with Mantis that accepts a version control (e.g. SVN, CVS) log message via stdin, and adds comments to any tickets as appropriate.
First things first. Create a new user in Mantis. This is the account the script will use. I called mine �svn�. Make sure the user has permission to add comments and resolve tickets. Don�t forget to add it to your project(s).
Open up /path/to/mantis/config_inc.php. If it doesn�t exist, create it. (If it doesn�t exist, you didn�t follow the installation directions.) This file is used to override default settings. It�s not distributed as part of Mantis, so when you upgrade, it won�t be overwritten. This is where you should have your database connection information, and where you would override the default colors, status/severity options, or any number of configurable settings.
You�ll notice I defined a regular expression different from the default. I wanted to not only match the string �issue #1337″, but to be a bit more liberal, matching the phrase �bug #1337″ too. For those of you savy enough to craft your own expressions, the first capturable group must be the bug number, or the script won�t work. (This is hard-coded into Mantis.) Hence the non-capturing group (?:bug|issue).

This is an undocumented setting. The default is to be equal to $g_source_control_regexp, but I only wanted certain tickets to be automatically closed, so I used a different regular expression. My expression matches �fixes issue #1337″, �fix bug #1337″, or simply �fixed #1337″. (Plus several iterations on those words.) The ticket number must be the first captured group. Altering the expression to also accept the words �solved� and �solves� is left as an exercise for the reader.

Before we go further, let�s make sure we implemented the Mantis settings properly. Run the following from the command line (alter the paths, of course)
%> /path/to/php /path/to/mantis/core/checkin.php <<< �My web monkey fixed issue #1337 by accident.�
If you�ve configured Mantis correctly, there should be a new comment on ticket #1337.
Now that we have Mantis set to accept log messages from our version control system, we need to connect Subversion to it. Remember the hooks from the beginning of this article? We�re going to write one. I used Bash script. (Be nice, I�m still learning Bash.)
The program svnlook is distributed as part of Subversion. Given a revision and repository path as parameters, it will return various properties of the revision, such as the author or which files were changed. In this case we�re asking only for the log message.
There you have it. That�s how you integrate Subversion with Mantis. If you have questions, feel free to leave a comment.
I wasn�t content with having just a log message added to my Mantis tickets. I wanted to know who did it, and what files were changed. Thus, my actual script is a bit more complicated. (Remember, I�m still learning Bash, so be nice.)
One Response to �Integrating Mantis and Subversion�

andere poging

23:49:53, December 15, 2004

- Comments (6)

In Net MRG's? bugtracker, I always thought it'd be nice to have a comment every time a commit to a bug was made. That way everyone involved would know when changes were being made, and what changes. Luckily, Mantis allows for this via its Source Control Integration.
If only it were that easy.
To make a long story short; whenever you start a project like this – use a separate CVSROOT – it will make your life much easier.
My loginfo
netmrg /usr/bin/php -q /path/to/mantisbt/core/checkin.php
ALL /usr/local/bin/syncmail -S "Net MRG- CVS?: " -R return@addr --quiet %%s to@addr
My mantisbt config_inc.php
$g_source_control_notes_view_status = VS_PUBLIC;
$g_source_control_account = 'netmrgcvs';
$g_source_control_set_status_to = OFF;
$g_source_control_regexp = «/bug\s*[#]{0,1}(\d+)/i»;
Nils Drews (buells@gmx.net) at 08:44:27, January 08, 2005
How does this work?? You write in your comment for the svn/cvs commit simply: bug #XXX solved and now in the notes of mantis it says exactly so?? And what is that loginfo file you wrote?? I think it's the key to run that script with each commit, but i don't know exactly. Thx for your help, Nils
Douglas E. Warner (http://www.silfreed.net) at 15:45:10, January 08, 2005
Yes, it will add a comment to the correct bug (er, Issue) about the stuff you just commited. This is for CVS; I haven't gotten around to setting this up again for subversion. The loginfo file is a file in your CVSROOT directory; I would recommend reading at cvshome.org.
Ivan Zhekov (izhekov@ppartner.com) at 07:06:16, June 10, 2005
loginfo is a configuration file of CVS. It's located in CVSROOT in the repository. So the idea is that every time you submit a bug, the log output is sent to the script checkin.php that verifies the log and write info about it in mantis database.
Chris (mkgnu@gmx.net) at 14:04:55, June 27, 2005
You may find it more valuable in the long term to use Scmbug: http://freshmeat.net/projects/scmbug/
nik at 16:29:00, October 30, 2006
beware: scmbug has a list of dependencies a mile long.
Doug (http://www.silfreed.net) at 19:09:20, October 30, 2006
I'm thinking about trying out trac (http://trac.edgewall.org/) to integrate everything for Net MRG?. I don't like the default look, but I'm hoping that can be fixed.

Deletions:

« Joint Education Meeting
Do you want to know how to integrate Mantis and SVN? I did, but could never manage the right Google query to return a page written for someone unfamiliar with customizing Mantis. (I�
�m still learning SVN too.) This is the documentation I wish I�

�d had. This process is easier if you know Bash or some other scripting language. This was accomplished using Mantis 1.0.0rc2. An older version may not work with these instructions.

Revision properties such as log messages aren�
�t versioned. If you were to go back and change a log message, for example, the old one would be lost. This hook, and its post- counterpart, offer a chance to reject or log the change.

Well, that sounds simple. All we have to do is write a script that will log into our bug tracking system and insert a comment on the appropriate ticket. That sounds easy enough, but let�
�s not make things too complicated. With a few minor customizations, Mantis will do most of the work for us.
The manual for Mantis has two relevant pages. One, titled �

�Source Control Integration�

�, provides a list of customizable settings, but offers no directions on where these settings are most appropriately accessed. The other, �

�CVS integration�

�, is not terribly helpful either, but it does provide another piece of our puzzle�
�it tells us there is a command line PHP script included with Mantis that accepts a version control (e.g. SVN, CVS) log message via stdin, and adds comments to any tickets as appropriate.
First things first. Create a new user in Mantis. This is the account the script will use. I called mine �
�svn�
�. Make sure the user has permission to add comments and resolve tickets. Don�
�t forget to add it to your project(s).
Open up /path/to/mantis/config_inc.php. If it doesn�
�t exist, create it. (If it doesn�t exist, you didn�t follow the installation directions.) This file is used to override default settings. It�s not distributed as part of Mantis, so when you upgrade, it won�t be overwritten. This is where you should have your database connection information, and where you would override the default colors, status/severity options, or any number of configurable settings. You�ll notice I defined a regular expression different from the default. I wanted to not only match the string �issue #1337″, but to be a bit more liberal, matching the phrase �bug #1337″ too. For those of you savy enough to craft your own expressions, the first capturable group must be the bug number, or the script won�t work. (This is hard-coded into Mantis.) Hence the non-capturing group (?:bug|issue). This is an undocumented setting. The default is to be equal to $g_source_control_regexp, but I only wanted certain tickets to be automatically closed, so I used a different regular expression. My expression matches �fixes issue #1337″, �fix bug #1337″, or simply �fixed #1337″. (Plus several iterations on those words.) The ticket number must be the first captured group. Altering the expression to also accept the words �solved� and �solves� is left as an exercise for the reader. Before we go further, let�s make sure we implemented the Mantis settings properly. Run the following from the command line (alter the paths, of course) %> /path/to/php /path/to/mantis/core/checkin.php <<< �My web monkey fixed issue #1337 by accident.� If you�ve configured Mantis correctly, there should be a new comment on ticket #1337. Now that we have Mantis set to accept log messages from our version control system, we need to connect Subversion to it. Remember the hooks from the beginning of this article? We�re going to write one. I used Bash script. (Be nice, I�m still learning Bash.) The program svnlook is distributed as part of Subversion. Given a revision and repository path as parameters, it will return various properties of the revision, such as the author or which files were changed. In this case we�re asking only for the log message. There you have it. That�s how you integrate Subversion with Mantis. If you have questions, feel free to leave a comment. I wasn�t content with having just a log message added to my Mantis tickets. I wanted to know who did it, and what files were changed. Thus, my actual script is a bit more complicated. (Remember, I�m still learning Bash, so be nice.) One Response to �Integrating Mantis and Subversion�

2006-12-16 12:02:35

Comparison for /Integration Mantis Subversion of 2006-12-16 12:02:35 and 2006-12-16 12:08:05

Deletions:

Add Your Comment
Name (required)
Mail (will not be published) (required)
Website

- Home
- About
- Entries (RSS)
- Comments (RSS)

MyWackoSite - IntegrationMantisSubversion

2006-12-16 12:08:05

andere poging

2006-12-16 12:02:35