Overview

Concurrent Versions System (CVS) is a popular open source SCM. CVS support in pulse? uses a pure Java cvs client and thus has no external dependencies.

Configuration

root

The cvs root identifies the path to the cvs repository. The path to the repository may be preceeded by an access method, username, host, and port, according to the following syntax:

    [:method:][[user][:password]@][hostname[:[port]]]/path/to/repository

The supported connection methods are

• local
• fork
• pserver
• ext (uses ssh to establish the connection to the repository host)

Examples

When connecting to a cvs repository on the same host as the pulse™ server, the :local: access method is optional. Here is an example where the access method is explicitly defined.

:local:/path/to/repository 

and here is an equivalent example where the :local: access method is dropped.

/path/to/repository 

When using the pserver access method, you must specify the cvs repository host. Here is an example of a using the :pserver: acces method.

:pserver:your.cvs.host:/path/to/repository

and here is an example where the user is defined. You will use this format when your cvs repository requires authenticated access.

:pserver:user@your.cvs.host:/path/to/repository

This field is required.

module

The module field defines your projects cvs module. If you have not defined a cvs module, then specify the path to the root of your project relative to the repository root.

For details on cvs modules, consult the documentation.

This field is required.

password

If your cvs repository requires authenticated access this field specifies the password used to authenticate the user.

This field is optional.

branch

To build your project from a cvs branch, specify the cvs branch here. If left blank, the cvs repository head is used.

This field is optional.

quiet period

Because cvs does not support atomic commits, it is possible for pulse™ to trigger a build after detecting the start of a long running commit. The resulting build will more often than not incorrectly signal a build failure. By specifying a quiet period, you are telling pulse™ to wait for a period of repository inactivity that is at least as long as the quiet period before triggering a build.

This field is optional.

monitor

The monitor field defines whether or not the configured SCM will be monitored for changes. By default, this value is set to true.