This page contains descriptions of the fields and options available when setting up VCS roots using Perforce:

If you plan to use agent-side checkout mode, note that Perforce client must be installed on the agents, and path to p4 executable must be added to the PATH environment variable.

P4 Connection Settings




Specify the Perforce server address. The format is host:port.


Click this radio button to directly specify the client workspace. The workspace should already be created by Perforce client applications like P4V or P4Win. Only mapping rules are used from the configured client workspace. The client name is ignored.

When this option is used, internal TeamCity source caching on the server side is disabled, which may worsen the performance of clean checkouts. For maximum performance, we recommend using Client Mapping option (see below)

Client Mapping

Click this radio button to specify the mapping of the depot to the client computer.
If you have Client mapping selected, TeamCity handles file separators according to OS/platform of a build agent where a build is run. To enforce specific line separator for all build agents, use Client having LineEnd option specified in Perforce instead of Client mapping. Alternatively you can add an agent requirement to run builds only on specific platform.

Use team-city-agent instead of the client name in the mapping.


//depot/MPS/... //team-city-agent/...
//depot/MPS/lib/tools/... //team-city-agent/tools/...


Specify the user login name.


Specify the password.


Select the character set used on the client computer.

Ticket-based authentication

Check this option to enable ticket-based authentication.

Path to Perforce Command-Line Client

Specify the path to the Perforce Command-Line Client (usually, it's p4.exe file).

See also:

Administrator's Guide: VCS Checkout Mode