Perforce

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

P4 Connection Settings
Changes Checking Interval
VCS Root Sharing

Icon

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

Option	Description
Port	Specify the Perforce server address. The format is host:port.
Client	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. Performance impact Icon 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. Tip Icon Use team-city-agent instead of the client name in the mapping. Example:
User	Specify the user login name.
Password	Specify the password.
Charset	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).

Changes Checking Interval

Option

Description

Checking interval

Select here how often TeamCity should check for VCS changes. By default the global predefined server setting is used, that can be modified at the Administration > Server Configuration page. The interval's time starts being counted as soon as the last VCS server poll is finished. Here you can specify here custom interval for the current VCS root.

Icon

Some public servers can block access if polled frequently.

VCS Root Sharing

Option	Description
VCS Root Sharing	Enable this option to use this VCS root in other projects or build configurations. See Shared VCS Roots for more information.

See also:

Administrator's Guide: VCS Checkout Mode