Build Checkout Directory
The build checkout directory is the directory where all of the project's sources reside. If the VCS checkout mode property of the build configuration is set to Automatically on server or Automatically on agent, TeamCity places the sources into the checkout directory according to the mapping defined in the VCS Checkout Rules.
If not specified, automatically created directory is used with a generated name: < >/<VCS settings hash code>. The VCS settings hash code is calculated based on VCS roots and VCS settings used by the build configuration. Effectively, this means that the directory is shared between all the build configurations with the same VCS settings.
If you want to investigate some issue and need to know the directory used by a build configuration, you can get the directory from the build log, or you can refer to < >/directory.map generated file which lists build configurations with their last used directories.
If for some reason default directory does not match your requirements (for example, the process of creating builds depends on some particular directory), you may want to 2.Version Control Settings.
Please note that content of the checkout directory can be deleted by TeamCity under Clean Checkout.
As a kind of failover measure TeamCity automatically performs Clean Checkout, if it finds files of another build configuration in the current checkout directory or the directory is empty.
In your Build Script Interaction with TeamCity you may refer to the effective value of build checkout directory via the teamcity.build.checkoutDir Properties of a Build Configuration provided by TeamCity.
Automatic Checkout Directory Cleaning
Checkout directories are automatically deleted from disk if not used (no builds use it as checkout directory) for a specified period of time (8 days by default). This behavior only applies to checkout directories created under the agent work directory (i.e. default checkout directories and custom checkout directories defined using relative paths).
The time frame can be changed by specifying new value (in hours) by either of the following ways:
'teamcity.agent.build.checkoutDir.expireHours'Defining Properties in thebuildAgent.propertiesfile;'teamcity.build.checkoutDir.expireHours'Properties of a Build Configuration
Setting the property to "0" will cause deleting the checkout directories right after the build finish.
The directory cleaning is performed in background and can be paused by consequent builds.
old section name for obsolete anchors:
Ensuring Free Disk Space Before the Build
Before the build is run on the agent, TeamCity checks the available free space. If build agent does not have required free disk space, build agent tries to free the disk space by
forcing delete of obsolete Checkout Directories that were pushed to background (see previous section);
deleting contents of other build's checkout directories in the Last Recently Used order (only default checkout directories can be cleaned).
The disk space check is performed for two locations: Agent Home Directory and build checkout directory.
By default, the required free space is 3Gb.
You can specify the free space value for a build agent in its buildagent.properties file or change the default value for a particular build configuration by specifying its system properties.
Required free space value is defined by the following properties:
Set
teamcity.agent.ensure.free.spacewith bytes to ensure space under build checkout directory.Set
teamcity.agent.ensure.free.temp.spacewith bytes to ensure space under 'temp' directory. Ifteamcity.agent.ensure.free.temp.spaceis not defined, the value ofteamcity.agent.ensure.free.spaceproperty will be used.
TeamCity checks the values in the following order:
build configuration system property
buildAgent.propertiesfile propertyif no specified property values found, then TeamCity uses the default value — 3Gb.
Generally, the teamcity.agent.ensure.free.space property value is set in bytes. Also, you can specify the value in kb, mb, gb, kib, mib, or gib.