CVS integration

Use

BUGtrack’s integration with CVS includes the following actions:

1. When a user checks in a file in CVS, he or she adds a comment containing the number of the related bug at the very beginning of the comment or elsewhere in the text preceded with the pound sign. For instance, the user begins his or her comment with ‘123456’ string or includes ‘#123456’ in any other part of the text to show that the check-in is related to bug number 123456.

2. As soon as the source file is checked in, CVS automatically launches the log handler, which sends the relevant data to your BUGtrack system if the check-in comment contains a bug ID.

3. When users access these records in BUGtrack, they can see a separate Checkins section in each record with hyperlinks to each check-in. Clicking on a link starts a locally installed CVS protocol handler and opens the corresponding file version differences for local viewing.

Procedure – CVS server

Your CVS system must be configured in order to properly update your BUGtrack database.

Step one. Check out the CVSROOT directory using command prompt.

Step two. Download the CVSupdate.zip file, extract and save ‘CVSupdate.wsf’ script file in the CVSROOT directory.

Step three. Add CVSupdate.wsf to the CVS repository using the command prompt.

Step four. Open CVSupdate.wsf for editing and set the License variable’s value to your BUGtrack license number.

Step five. Open the file ‘loginfo’ (located in the CVSROOT directory) for editing and add the following line at the end of the file: ALL CSCRIPT //NOLOGO C:/CVSREP/CVSROOT/CVSupdate.wsf “%{sVv}”

Step six. Open the file ‘checkoutlist’ (located in the CVSROOT directory) for editing and add the following line at the end of the file: CVSupdate.wsf Error - missing CVSupdate.wsf

Step seven. Check in the file changes using the command prompt.

Procedure – Client

Every client computer on which users are supposed to view check-ins using hyperlinks in bugs should have CVS protocol handler installed, and the users should be authorized to access your CVS database.

Step one. Download the CVSViewer.exe file and save it locally.

Step two. Register the file using the command prompt (run VSSViewer.exe /register).

Step three. Configure the template for opening the file for viewing differences using the command prompt: CVSViewer.exe /template <template string>. The <template string> defines which application should open which URL to view the differences. In the template URL string, the following placeholders for real values can be used:

Thus, the template configuration command for viewing file version differences with Internet Explorer from the ‘someserver’ server may be the following string:

CVSViewer.exe /template iexplore.exe "HTTP://someserver/viewcvs/{s}.diff?r1={V}&r2={v}"

Next: Using BUGtrack