For the latest version, visit http://www.badgers-in-foil.co.uk/projects/cvsspam/.
To install CVSspam you'll need to alter the repository's configuration files.
Check out your repository's CVSROOT.
Alter commitinfo to call the CVSspam script that records the directories that have been commited:
Now you need to alter loginfo to record the log entry made by the user (and send off the email):
![]() | The expression you use to select the project (the first thing on the line) must be the same in commitinfo and loginfo. |
Commit your changes to these files. You should see a message from CVS like 'rebuilding adminstrative database'. You are now be ready to test the setup.
Checkout a copy of myproject and commit a change. An email should be sent to the address you specified.
The CVSspam scripts may be located anywhere in the CVS server's filesystem.
It's common to place these files inside the repository's CVSROOT, and this can be the only option if CVS is the only way you have to access a remote server. To do this, you need a checked-out copy of the CVSROOT, as described above. Place record_last_dir.rb, collect_diffs.rb and cvsspam.rb into this directory.
Add these three filenames into CVSROOT/checkoutlist
cvs add the three scripts to the repository, then cvs commit them, and the modified checkoutlist.
In commitinfo and loginfo you can now refer to the scripts with $CVSROOT/CVSROOT/record_lastdir.rb and $CVSROOT/CVSROOT/collect_diffs.rb
You can specify CVSspam options in a configuration file. By default, the file $CVSROOT/CVSROOT/cvsspam.conf is used, though you can specify another with the --config option to collect_diffs.rb.
If you want to put your config into the repository, follow the instructions above for installing files into CVSROOT
To see the available options, see the example cvsspam.conf provided.
Did you specify the right email address?
Does the regular expression you specified in commitinfo and loginfo really match the project? Try changing the entry to something like
When you commit a change to myproject, 'Hello world' should appear in your terminal. If it doesn't, check that expression on the left is correct.Check that the CVS server corectly handles email. By default CVSspam invokes sendmail. Try running sendmail by hand on the CVS server machnine
The cvs executable is probably not in the default executable search path available to the CVSspam scripts. Tell them explicitly where to find cvs by setting the $cvs_prog option in the configuration file.
CVSspam can generate simple links to web based bug tracking systems, currently supporting Bugzilla and JIRA.
For bugzilla, when a CVS log comment contains text like Fix for bug 123..., the text "bug nnn" will become a hyperlink to that Bugzilla page in the generated email.
To enable, give your Bugzilla's URL in CVSspam's configuration file
The marker %s tells CVSspam where in the URL to put the bugId from the log message.For JIRA, include the issueId in the log comment. JIRA issue Ids have a project name and issue number, seperated by a dash. For example JRA-1545.
To enable, give your JIRA installation's URL in CVSspam's configuration file
The marker %s tells CVSspam where in the URL to put the issue Id from the log message.For systems that like to talk about tickets, CVSspam will make links from text in the log comment that looks like "bug nnn" (where nnn is a number). For instance with RT, supply the location of Display.html
If you have ViewCVS, CVSweb or Chora web-access to your repository, CVSspam can generate links to it in the emails. Links the file before and after the commit are very useful for images, as only changes to binary text files are mailed. You'll get a link to the side-by-side view of the changes as well.
To enable ViewCVS support, specify the URL of the top-level ViewCVS directory in cvsspam.conf.
For CVSweb, specify the URL of cvsweb.cgi,
For Chora, specify the URL of the directory containing cvs.php,
Recipient email addresses can be put in the configuration file as well as in each loginfo entry. For example,