...
Option | Description | |||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Specify the Perforce server address. The format is | |||||||||||||||||||||||||||
| Click this radio button to specify an existing Perforce stream. TeamCity will use this stream to prepare the stream-based workspace, and will use the client mapping from such a workspace. Prior to TeamCity 2017.2, TeamCity supports streams stored one level below the depot name: the format is //streamdepot/streamname.
Prior to TeamCity 2017.2, TeamCity supports streams stored one level below the depot name: the format is //streamdepot/streamname. Parameters are supported. For the
| |||||||||||||||||||||||||||
| Click this radio button to directly specify the client workspace name. The workspace must be already created by a Perforce client application like P4V or P4Win. Only the mapping rules from the configured client workspace are used. The client name is ignored.
| |||||||||||||||||||||||||||
| Click this radio button to specify the mapping of the depot to the client computer.
Example:
Since TeamCity 10.0, Now Clean Checkout on a client mapping change is not enforced for the agent-side checkout in the following cases:
| |||||||||||||||||||||||||||
| Specify the user login name. | |||||||||||||||||||||||||||
| Specify the password or ticket. If this field is specified, TeamCity
If the password is not specified at all, TeamCity relies on an existing p4 ticket for the current user (p4ticket.txt), and if the ticket is not present, it will fail. The ticket file, should be present on all build agents where TeamCity runs perforce builds for this VCS root and on the TeamCity server (as the server also executes perforce commands) | |||||||||||||||||||||||||||
| Check this option to enable ticket-based authentication. |
Case-Insensitivity in Checkout Rules
...
Option | Description | ||||||
---|---|---|---|---|---|---|---|
| If needed, you can set here the following options for the | ||||||
Create non-stream workspace | (Since TeamCity 2018.2) This option is available only when 'Stream' is selected in Connection Settings. Enable the option to be able to checkout using a non-stream workspace based on the stream specification. This allows using checkout rules but makes it impossible to commit to the stream within the build. | ||||||
Run 'p4 clean' for cleanup | Enable this option to clean up your workspace from extra files before a build (since p4 2014.1) When enabled, the | ||||||
Skip the have list update: | Enable this option not to track files on the Perforce server on sync (always transfer all files to the agent, p4 sync -p) | ||||||
Extra sync options | Specify additional 'p4 sync' options, like |
...
P4 path on the build agent
| Specify the path to the Perforce command-line client: Prior This field works only on the agent side for agent-side checkout (prior to TeamCity 2017.2.2 this path was be used for both the server-side checkout and the agent-side checkout. Since TeamCity 2017.2.2 this field works only on the agent side for agent-side checkout. ). To restore old behavior, the | ||||||||
| If you need to check out sources not with the latest revision, but with a specific Perforce label (with selective changes), you can specify this label here. For instance, this can be useful to produce a milestone/release build, or a reproduce build. If the field is left blank, the latest changelist will be used for sync.
| ||||||||
| Select the character set used on the client computer. | ||||||||
| Enable this option if you have You may want to enable this option if you use server-side checkout and have files of the If you store |
...