Mantis integration with CVS
Moderators: Developer, Contributor
-
Silver Lao
Mantis integration with CVS
Dear Friends:
I am a developer in a logistic station in GZ China, maintaining a logistic system, leading 3 to 4 programers work together, I found mantis is very useful tool for my work. So thank you all who write the code!
I found mantis is lack of integration with CVS source code inspection and project timeline monitoring. So I just start to code them immediately, I had write some code, but util today, I wake up and think maybe someone had already done it before. So I come to ask if someone had related codes?!
Here the features I had complete (not sorted):
1. Submit the source code with writing the comment like "issue #nn,issue #nn" in any CVS client to solve one or more issue.
2. The CVS change info will show at issue's history list, click on the relate history will show the diff result, and auto generate and maintain the source code check list in the additional information
3. The CVS change info will also show at a "CVS change log" page to list out who and when submit the changes, and the issue's category and project name
4. The "CVS change log" admin jobs, batch move the changes to other issue (for wrong input issue ID when submit), delete changes....
Here the features I continous developing.......
5. From the "CVS change log" generate a ZIP file that including the changes files by some condition (category, version......)
6. Regenerate the Issue's check list .
7. A set of project monitoring page link the graph of issue relationship that can see the gantt picture of the project's issue and can click on the issue link to the issue info. page
Do you ever done it, give me your idea please!
I modify the checkin.php and write a postcommit.php to verify and log the CVS info from CVSROOT's verifymsg and loginfo file to get the changes infomation, and use View-CVS as the CVS explorer to get the diff.
I found the Chinese Translation is dirty, miss some words, can the I18N files changes to UTF8 encoding?! ( I think it in my Java brain, maybe not work, please tell me )
I am a developer in a logistic station in GZ China, maintaining a logistic system, leading 3 to 4 programers work together, I found mantis is very useful tool for my work. So thank you all who write the code!
I found mantis is lack of integration with CVS source code inspection and project timeline monitoring. So I just start to code them immediately, I had write some code, but util today, I wake up and think maybe someone had already done it before. So I come to ask if someone had related codes?!
Here the features I had complete (not sorted):
1. Submit the source code with writing the comment like "issue #nn,issue #nn" in any CVS client to solve one or more issue.
2. The CVS change info will show at issue's history list, click on the relate history will show the diff result, and auto generate and maintain the source code check list in the additional information
3. The CVS change info will also show at a "CVS change log" page to list out who and when submit the changes, and the issue's category and project name
4. The "CVS change log" admin jobs, batch move the changes to other issue (for wrong input issue ID when submit), delete changes....
Here the features I continous developing.......
5. From the "CVS change log" generate a ZIP file that including the changes files by some condition (category, version......)
6. Regenerate the Issue's check list .
7. A set of project monitoring page link the graph of issue relationship that can see the gantt picture of the project's issue and can click on the issue link to the issue info. page
Do you ever done it, give me your idea please!
I modify the checkin.php and write a postcommit.php to verify and log the CVS info from CVSROOT's verifymsg and loginfo file to get the changes infomation, and use View-CVS as the CVS explorer to get the diff.
I found the Chinese Translation is dirty, miss some words, can the I18N files changes to UTF8 encoding?! ( I think it in my Java brain, maybe not work, please tell me )
Re: Mantis integration with CVS
Dear Friend:
I want to generate CVS's passwd and commit_avail files from Mantis automatic. After check the CVS manual it use standard Crypt() to generate the password string (8 digit), but I found the Mantis's Crypt type login_method's password is not same(16 digit), how can I fix it, any idea?!
Regards
Silver
I want to generate CVS's passwd and commit_avail files from Mantis automatic. After check the CVS manual it use standard Crypt() to generate the password string (8 digit), but I found the Mantis's Crypt type login_method's password is not same(16 digit), how can I fix it, any idea?!
Regards
Silver
-
laowf@21cn.com
I had done!
Does anyone like it?! I can not find a way to publish it!
Email to me if you want it !
Including:
1. CVS action monitoring
2. Auto get source code from CVS and handover jobs in a ZIP file.
3. Issue's schedule and status monitoring(Gantt)
Email to me if you want it !
Including:
1. CVS action monitoring
2. Auto get source code from CVS and handover jobs in a ZIP file.
3. Issue's schedule and status monitoring(Gantt)
-
Silver Lao
Done the integration
Please have a look at
http://sightstyle.gnway.net/blog/index.php?blogId=1
or the demo site
http://sightstyle.gnway.net/issue/
http://sightstyle.gnway.net/blog/index.php?blogId=1
or the demo site
http://sightstyle.gnway.net/issue/
-
Tobias Meyer
-
Tobias Meyer
Because I believe in diversity, a cross-post to the manual and scmbug.
http://manual.mantisbt.org/manual.insta ... ration.php
http://freshmeat.net/projects/scmbug/
SCMBug has very harsh dependencies for a perl script, but seems to be a promising approach to integrate different Source-control systems (CVS, Subversion, etc. ) to different issue trackers (including mantis).
It seems to be somewhat limited (as of ver. 0.8.5), as it only supports adding notes to issues, no resolving them or alike. (please someone correct me if I'm wrong)
If silver's approach allows for that, I definitely go for that...
http://manual.mantisbt.org/manual.insta ... ration.php
http://freshmeat.net/projects/scmbug/
SCMBug has very harsh dependencies for a perl script, but seems to be a promising approach to integrate different Source-control systems (CVS, Subversion, etc. ) to different issue trackers (including mantis).
It seems to be somewhat limited (as of ver. 0.8.5), as it only supports adding notes to issues, no resolving them or alike. (please someone correct me if I'm wrong)
If silver's approach allows for that, I definitely go for that...
-
Silver Lao
Add a source respository for you diff
can see the cvs log is relate to the issue number.
and you can get the source code from the file content
http://sightstyle.gnway.net/cgi-bin/vie ... cvshandle/
and you can get the source code from the file content
http://sightstyle.gnway.net/cgi-bin/vie ... cvshandle/
-
Silver Lao
Hi Silver,
I think your work is great, although there are projects specialising in integrating Mantis with source control (i.e. scmbug), I always believed that there should be some sort of out-of-the-box integration. I believe that this should be for at least CVS and SVN.
Please contact me so that we can co-ordinate how your code can be integrated into Mantis core, and how easy it is to keep it generic so that it can work CVS and SVN, and potentially any other source control that can generate the events we are expecting.
Regards,
Victor
Mantis Blog
http://www.futureware.biz/
I think your work is great, although there are projects specialising in integrating Mantis with source control (i.e. scmbug), I always believed that there should be some sort of out-of-the-box integration. I believe that this should be for at least CVS and SVN.
Please contact me so that we can co-ordinate how your code can be integrated into Mantis core, and how easy it is to keep it generic so that it can work CVS and SVN, and potentially any other source control that can generate the events we are expecting.
Regards,
Victor
Mantis Blog
http://www.futureware.biz/
Has anyone continued with this?
vboctor wrote:Hi Silver,
I think your work is great, although there are projects specialising in integrating Mantis with source control (i.e. scmbug), I always believed that there should be some sort of out-of-the-box integration. I believe that this should be for at least CVS and SVN.
Please contact me so that we can co-ordinate how your code can be integrated into Mantis core, and how easy it is to keep it generic so that it can work CVS and SVN, and potentially any other source control that can generate the events we are expecting.
Regards,
Victor
Mantis Blog
http://www.futureware.biz/
I would love to try it, but have no idea how to install it. Tried scmbug project. For some reason they want issues to have assigned status. Also it limits you to getting notifications on the file change. How about accessing code through webcvs, looking in the diffs like in FogBugz, etc ...