Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
Version 1
Next »
 |
You are viewing documentation of TeamCity 6.5.x, which is not the most recent released version of TeamCity. Please refer to the listing to choose another version.
|
Search
Table of Contents
|
This page contains descriptions of the fields and options available when setting up VCS roots using Perforce:
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.
|
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.
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.
|
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:
|