CVS

Common VCS Root properties Configuring VCS Roots.

This page contains descriptions of CVS-specific fields and options available when setting up a VCS root. Depending on the selected access method, the page shows different fields that help you to easily define the CVS settings:

CVS Root

Option	Description
Module name	Specify the name of the module managed by CVS.
CVS Root	Use these fields to select the access method, point to the user name, CVS server host and repository. For example: `':pserver:user@host.name.org:/repository/path'`. For a cvsLocalCvsOptionsDescription} connection only the path to the CVS repository should be used. TeamCity supports the following connection methods (described below): cvsPserverOptionDescription cvsExtProtocolOptionsDescription cvsSshProtocolCheckoutOptionsDescription cvsLocalCvsOptionsDescription}

Option

Description

Module name

Specify the name of the module managed by CVS.

CVS Root

Use these fields to select the access method, point to the user name, CVS server host and repository. For example: ':pserver:user@host.name.org:/repository/path'. For a cvsLocalCvsOptionsDescription} connection only the path to the CVS repository should be used. TeamCity supports the following connection methods (described below):

cvsPserverOptionDescription
cvsExtProtocolOptionsDescription
cvsSshProtocolCheckoutOptionsDescription
cvsLocalCvsOptionsDescription}

Checkout Options

Option	Description
Checkout HEAD revision Checkout from branch Checkout by Tag	Define the way CVS will fill in and update the working directory
Quiet period	Since there are no atomic commits in CVS, using this setting you can instruct TeamCity not to take (detect) a change until the specified period of time passed since the previous change was detected. It helps avoid situations when one commit is shown as two different changes in the TeamCity web UI.

PServer Protocol Settings

Option	Description
CVS Password	Click this radio button if you want to access the CVS repository by entering a password.
Password File Path	Click this radio button to specify the path to the `.cvspass` file.
Connection Timeout	Specify the connection timeout.

Ext Protocol Settings

Option	Description
Path to external rsh	Specify the path to the rsh program used to connect to the repository.
Path to private key file	Specify the path to the file that contains user authentication information.
Additional parameters	Enter any required rsh parameters that will be passed to the program. Multiple parameters are separated by spaces.

SSH Protocol Settings (internal implementation)

Option	Description
SSH version	Select a supported version of SSH.
SSH port	Specify SSH port number.
SSH Password	Click this radio button if you want to authenticate via an SSH password.
Private Key	Click this radio button to use private key authentication. In this case specify the path to the private key file.
SSH Proxy Settings	See cvsPserverProxySettingsOptionDescription.

Local CVS Settings

Option	Description
Path to the CVS Client	Specify the path to the local CVS client.
Server Command	Type the server command. The server command is the command which makes the CVS client to work in server mode. Default value is `'server'`

Proxy Settings

Option	Description
Use proxy	Check this option if you want to use a proxy, and select the desired protocol from the drop-down list.
Proxy Host	Specify the name of the proxy.
Proxy Port	Specify the port number.
Login	Specify the login.
Password	Specify the password.

Advanced Options

Option	Description
Use GZIP compression	Check this option to apply gzip compression to the data passed between the CVS server and the CVS client.
Send all environment variables to the CVS server	Check this option to send environment variables to the server for compatibility with certain servers.
History Command Supported	Check this option to use the history file on the server to search for newly committed changes. Enable this option to improve the CVS support performance. By default, the option is not checked because not every CVS server supports keeping a history log file.

Last modified: 20 April 2023