Version Control Settings
Administration > <project> > <build configuration> > Version Control Settings or
Administration > Configure VCS roots > <vcs root> > Version Control Settings
This page describes the options available on the Version Control Settings page when editing build configurations.
VCS Roots
| Option |
Description |
| <VCS root name> |
A table of existing VCS roots will appear if they are already attached to the build configuration. Click the name or edit to modify it, detach to remove the VCS root from build configuration (it will not be deleted from the project). Click edit checkout rules to view or change the selected VCS root's checkout rules. |
| Attach existing VCS root |
This item will appear if the project contains VCS roots that are not already attached to the particular build configuration. Select the VCS root from the drop-down list to attach it to the build configuration and add it to the table listed above. |
| Create and attach new VCS root |
Click this link to attach a new VCS root. You will be redirected to the create VCS root page. |
Checkout Settings
| Option |
Description |
| VCS checkout mode |
Select the desired VCS checkout mode from the drop-down list. Options include: Automatically on server (the TeamCity server will check out the sources and pass them to an agent before each build), Automatically on agent (the build agent will check out the sources before the build), and Do not check out files automatically (TeamCity will not check out any sources. The build script will contain the commands to check them out). Note: Agent-side checkout is only supported for CVS and Subversion. |
| Checkout directory |
Specify the directory on the agent where you want the sources to be checked out to and the build process to start. Leave this field blank to use the agent's default Build Checkout Directory. |
| Clean all files before build |
Check this option to remove all of the residual information left by the build runner that might impede the next build of the same configuration. If this option is checked, TeamCity performs a full checkout of the entire project before each build.
 | This feature is located on this page in TeamCity 3.1+. If you are using version 3.0 please look for this option under build options on the General Settings page. |
|
 | If you use several VCS roots for a single build configuration, you will probably need to configure VCS checkout rules to specify to which directory each root will be checked out. |
VCS Labeling
| Option |
Description |
| VCS labeling mode |
Click a radio button to choose the VCS labeling mode. The possible options are:
- Do not label: disable labeling
- Successful only: label successful builds only
- Always: label all builds
|
| Labeling pattern |
This field can be edited if VCS labeling is enabled. The label consists of the build name and number using the following format: <labelname>%system.build.number%. |
| Choose VCS roots to label |
Check each build configuration to be labeled. |
Changes Checking Interval
| Option |
Description |
| Checking interval |
Select a radio button to choose between the global server setting of 60 seconds and entering a custom interval.
| Some public servers 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: