Community
Participate
Working Groups
I'm on a software development team that has been using both eclipse and bugzilla for almost 3 years now. We love both of these tools, but are frustrated that there appears to be no obvious link between the two tools. We haven't been able to find any eclipse plugins that link the two tools together either. What we'd like to see implemented minimally is some way to notate a bug/issue number into files as they're being Committed into CVS from Eclipse. Some of our team members are good about putting the issue number into the CVS Comments field when checking changes into CVS, but others are not. And even the developers that do use the Comment field for this notation don't always use the exact same formatting for their issue notations. So it's nearly useless to even try. I recently modified my local copy of the org.eclipse.team.cvs.ui plugin to display an optional (default is off) dialog box that pops up right after you type in your CVS Comment, asking you to type in an issue number. Then it takes that issue number (String) and pre-pends it to the Comments that the user had just typed in before passing it on to be processed. It's a very small and simple change to this core eclipse plugin, and I think that a lot of development teams would be willing to use it if it were deployed with Eclipse. And the default behavior would be exactly the same as it is today. The user has to go into the Preferences in order to turn on the new dialog box. My first choice would have been to add a plugin to the existing cvs plugin that added this new dialog box to the process, but no Extension Points appear to have been implemented in the org.eclipse.team.cvs.ui plugin. So if the Eclipse development community doesn't think it's a good idea to implement an optional issue/bug number dialog box when committing files, please at least implement some appropriate Extension Points so that developers like myself can implement plugins to do the job, without having to hack into existing core plugins. If anyone wants to see the code changes I made to my local copy of the org.eclipse.team.cvs.ui plugin, please let me know and also let me know how you'd like to see it. I'm unsure how to upload a patch file, or even what format a patch file is. But I'd be more than happy to share my code changes with anyone who is interested in seing them. Thanks for listening, Kurt Leucht (from Florida)
Created attachment 41538 [details] My implementation of this feature request (from plugin version 3.1.0) I think I figured out how to make a patch file of my implementation of the enhancement request. There were 7 JAVA files and one properties file that I modified to implement my optional dialog box. Hope this example implementation helps show you what a simple change this feature is. And the payoff could be huge for many development teams out there.
Created attachment 41539 [details] Screenshot of modified Preferences page Here's what my example Preferences page looks like for the code modification that I implemented. By default, "Prompt for Issue Number during Commit" comes up "No", so it will act like it always did for most users who don't want the feature.
Created attachment 41540 [details] User types in an issue number You could add another configurable that swaps out the term "bug" for "issue" or whatever, just like the Bugzilla config allows for.
Created attachment 41541 [details] Or the user could leave it blank, even if the dialog was turned ON. Leaving it blank, will act like the old way, no change to the CVS Comment.
Created attachment 41542 [details] Here are the resulting CVS Comments from the 2 checkins The issue number is pre-pended to the CVS Comments if it is typed into the dialog box.
CVS already provides support for incorporating various types of validation before committing a file. Specifically, there are three types of programs that can be run on a commit operation: i)One for the validiation of files before they get committed ii)One for the validation of the log message to be committed with the files iii)One that receives the log message from a successful commit and does some post-commit operation (ie. sends an email out etc.) These scripts are run on the CVS server and are completely customizable. You should look into getting the second option going. To do this: 1. Your repo root has a CVSROOT folder in it. Inside are a bunch of config files. The ones you are interested in are verifymsg and rcsinfo. 2. verifymsg is called with the passed in log comment. You can write a shell script to check for certain conditions (ie. Bug number included) 3. rcsinfo is used to provide a comment template. You can write a template of what a commit comment should look like and it will appear each time someone does a commit. For more info, check out the online CVS manual. Under the Reference section, section C has an example of a verifymsg and rcsinfo file.
Created attachment 41612 [details] Commit using the rcsinfo comment template Note that any lines marked CVS: are not included in the comment.
Created attachment 41615 [details] verifymsg example Here's a pic of what happens when your log comment doesn't meet the criteria of your verifymsg script. Note that no commit will occur.
Ideally, what we would need is described in Bug 74351 - the ability to allow clients to contribute commit policies. Marking as duplicate of that. *** This bug has been marked as a duplicate of 74351 ***
(In reply to comment #0) > I'm on a software development team that has been using both eclipse and > bugzilla for almost 3 years now. We love both of these tools, but are > frustrated that there appears to be no obvious link between the two tools. We > haven't been able to find any eclipse plugins that link the two tools together > either. I know it's not exactly what you want, but the Bugzilla plugin has been getting some love since the initial work by someone at IBM. The work that's been done by Jeff Pound and Igor Foox over the past year or so is all in CVS and more information can be found here: http://sourceware.org/eclipse/bugzilla/ It'd be great to have more integration and the things you mention are just a few of the items we'd like to work on. We usually discuss things on fedora-devel-java-list@redhat.com but we can set up a sourceware.org mailing list if the traffic about Eclipse plugins gets too high :) I look forward to hearing from you and any other interested parties!
