Predefined Build Parameters
TeamCity provides a number of build parameters which are ready to be used in the settings of a build configuration or in build scripts.
The predefined build parameters can originate from several scopes:
Server build properties are generated by TeamCity on the server side in the scope of a particular build. An example of such parameter is a build number.
Agent properties are provided by an agent on connection to the server. They are not specific to any build and characterize the agent environment (for example, the path to the .NET framework). These are mainly used in agent requirements.
Agent build properties are provided on the agent side in the scope of a particular build right before the build start. For example, a path to a file with a list of changed files.
All these parameters are passed to a build.
There is also a special type of server-side build parameters that can be referenced by other parameters but that are not passed to a build. See Configuration Parameters below for the list of such parameters.
Server Build Properties
System properties can be referenced using %system.propertyName%.
System property name | Environment variable name | Description |
|---|---|---|
|
| The version of the TeamCity server. This property can be used to determine if the build is run within TeamCity. |
|
| The name of the project the current build belongs to. |
|
| The name of the build configuration the current build belongs to. |
| none | The unique ID used by TeamCity to reference the build configuration the current build belongs to. |
| none | The full name (including the path) of the file containing all the build properties in alphabetical order. |
|
| Is set to |
|
| The build number assigned to the build by TeamCity using the build number format. The property is assigned based on the build number format. |
| none | The internal unique ID used by TeamCity to reference builds. |
| none | A generated username that can be used to download artifacts of other build configurations. Valid only during the build. (Read more details ). |
| none | A generated password that can be used to download artifacts of other build configurations. Valid only during the build. (Read more details ). |
|
| The latest VCS revision included in the build for the root identified. See Configuring VCS Roots for the <VCS root ID> description. If there is only a single root in the configuration, the |
Configuration Parameters
Configuration parameters are parameters that can be referenced by other properties (only if defined on the Parameters page), but that are not passed to the build themselves.
You can get the full set of such server properties by adding the system.teamcity.debug.dump.parameters property to a build configuration and examining the "Available server properties" section in the build log.
Among these properties are the following:
Dependencies Properties
These are properties provided by the builds the current build depends on (via a snapshot or an artifact dependency ).
In a dependent build, dependencies properties have the following format:
<btID>— the ID of the build configuration to get the property from. Only the configurations the current one has snapshot or artifact dependencies on are supported. Indirect dependencies configurations are also available (for example, A depends on B and B depends on C — A will have C's properties available).<property name>— the name of the build parameter of the build configuration with the given ID.
Overriding Dependencies Properties
It is possible to redefine the build parameters in the snapshot-dependency builds when the current build starts. For example, build configuration A depends on B and B depends on C; on triggering, A can change any parameter used in B or C with the following property:
To change a parameter in all dependencies at once, use a wildcard:
Thus, each dependent build in a chain can redefine parameters in any of its dependency builds.
If build configurations A and B are trying to set different values for the same parameter in the build configuration C, the following rules apply:
if A depends on B by a snapshot dependency either directly or transitively, the value proposed by A will be used in C (and vice versa, if B depends on A)
- if both A and B do not depend on each other, TeamCity will consider it a conflict and will not modify the original value in C. Instead, two other parameters will be created for C:
conflict.<btA>.<property_name>=<valueA>conflict.<btB>.<property_name>=<valueB>
The reverse.dep.* parameters are processed on queuing of the build where the parameters are defined. As the parameters' values should be known at that stage, they can only be defined either as build configuration parameters or in the custom build dialog. Setting the parameter during the build has no effect.
Pushing a new parameter into the build will supersede the "Do not run new build if there is a suitable one" snapshot dependency option and may trigger a new build if the parameter is set to a non-default value.
Note that the values of the reverse.dep. parameters are pushed to the dependency builds "as is", without reference resolution. %-references, if any, will be resolved in the context of the build where the parameters are pushed to.
<property_name> is the name of the property to set in the noted build configuration. To set system property, <property_name> should contain the system. prefix.
VCS Properties
These are the settings of VCS roots attached to the build configuration.
VCS properties have the following format:
<VCS_root_ID>— is the VCS root ID as described on the Configuring VCS Roots page.<VCS_root_property_name>— the name of the VCS root property. This is VCS-specific and depends on the VCS support. You can get the available list of properties as described above. If there is only one VCS root in a build configuration, the<VCS root ID>.part can be omitted.
Properties marked by the VCS support as secure (for example, passwords) are not available as reference properties.
Branch-Related Parameters
When TeamCity starts a build in a build configuration where a branch specification is configured, it adds a branch label to each build. This logical branch name is also available as a configuration parameter:
To distinguish builds started on a default and a non-default branch, there is an additional boolean configuration parameter available since 7.1.5 which allows differentiating these cases:
For Git & Mercurial, TeamCity provides additional parameters with the names of VCS branches known at the moment of the build start. Note that these may differ from the logical branch name as per branch specification configured. This VCS branch is available from a configuration parameter with the following name:
where <VCS_root_ID> is the VCS root ID as described on the Configuring VCS Roots page.
Other Parameters
Parameter Name | Description |
|---|---|
| Human-friendly description of how the build was triggered |
| If the build was triggered by a user, the username of this user is reported. When a build is triggered not by a user, this property is not reported. |
Agent Properties
Agent-specific properties are defined on each build agent and vary depending on its environment. Aside from standard properties (for example, teamcity.agent.jvm.os.name or teamcity.agent.jvm.os.arch are provided by the JVM running on an agent) agents also have properties based on installed applications. TeamCity automatically detects a number of applications including the presence of .NET Framework, Visual Studio and adds the corresponding system properties and environment variables. A complete list of predefined agent-specific properties is provided in the table below.
If additional applications/libraries are available in the environment, the administrator can manually define the property in the <agent home>/conf/buildAgent.properties file. These properties can be used for setting various build configuration options, for defining build configuration requirements (for example, existence or absence of some property) and inside build scripts. For more information on how to reference these properties, see the Defining and Using Build Parameters in Build Configuration section.
In the TeamCity web UI, the actual properties defined on the agent can be reviewed by going to the Agents tab at the top navigation bar <Agent> | <Agent> page | the Agent Parameters tab:
Predefined Property | Description |
|---|---|
| The name of the agent as specified in the |
| The path to the Agent Work Directory. |
| Free space available in the Agent Work Directory. |
| The path to the Agent Home Directory. |
| The corresponding JVM property (see JDK help for properties description). |
| The corresponding JVM property (see JDK help for properties description). |
| The corresponding JVM property (see JDK help for properties description). |
| The corresponding JVM property (see JDK help for properties description). |
| The corresponding JVM property (see JDK help for properties description). |
| The corresponding JVM property (see JDK help for properties description). |
| The corresponding JVM property (see JDK help for properties description). |
| The corresponding JVM property (see JDK help for properties description). |
| The corresponding JVM property (see JDK help for properties description). |
| The corresponding JVM property (see JDK help for properties description). |
| The corresponding JVM property (see JDK help for properties description). |
| The corresponding JVM property (see JDK help for properties description). |
| See the section below for details. |
| The agent's OS bitness. |
| This property is defined if the corresponding version(s) of .NET Framework runtime is installed. (Supported versions are 1.1, 2.0, 3.5, 4.0- 4.6.1). |
| This property value is set to the corresponding framework runtime version(s) path(s). Note that this parameter is defined only for the latest installed version per major release. |
| This property is defined if the corresponding version(s) of .NET Framework SDK is installed. (Supported versions are 1.1, 2.0) |
| This property value is the path of the corresponding framework SDK version. |
| This property value is the path to the corresponding Reference assemblies (AKA Targeting Pack) location. (Supported versions are 2.0 - 4.6.1) |
| This property is defined if the corresponding version of Windows SDK is installed. (Supported versions are 6.0, 6.0A, 7.0, 7.0A, 7.1, 8.0, 8.0A, 8.1, 8.1A, 10) |
| This property value is the path of the corresponding version of Windows SDK. |
| This property is defined if the corresponding version(s) of Visual Studio is installed |
| This property value is the path to the directory that contains |
| This property value is the path to the directory that contains the standalone NUnit test launcher, |
| The property value is the path to the directory that contains the MSBuild task dll providing the NUnit task for MSBuild, Visual Studio (sln). |
| The property value is the path to the directory that contains MSBuild 2.0 listener and tasks assemblies. |
| The property value is the path to the directory that contains MSBuild 4.0 listener and tasks assemblies. |
| The agent port used by the TeamCity server to connect to the agent. |
| CPU benchmarking result for the agent. |
| The number of processors in the build agent system. |
| The name of the build agent host. |
Agent Environment Variables
An agent can define some environment variables. These variables can be used in build scripts as usual environment variables.
Java Home Directories
When a build agent starts, first the installed JDK and JRE are detected; when they are found, the Java-related environment variables are defined as described in the section below.
Detecting Java on Agent
The installed Java is searched for in the ALL locations listed below. Then, every discovered Java is launched to verify that it is a valid Java installation, and the Java version and bitness are determined based on the output.
The following locations are searched (a number of locations is common for all operating systems; some of them are OS-specific):
If defined, a custom directory on the agent is searched for Java installations. Defining a custom directory to search for Java is described below.
It is checked whether the
JAVA_HOME,JDK_HOME,JRE_HOMEvariables are definedThe OS-specific locations, listed in the next section, are checked
The
PATHenvironment variables are searched and the discovered directories are checked for containing Java
Windows
The Windows Registry is searched for the Java installed with the Java installer
C:\Program FilesandC:\Program Files (x86)directories are searched forJavaandJavaSoftsubdirectoriesthe
C:\Javadirectory is searched
Unix
The following directories are searched for Java subdirectories:
/usr/local/java/usr/local/usr/java/usr/lib/jvm/usr
macOS
The following directories are searched:
/System/Library/Frameworks/JavaVM.framework/Versions/<Java Version>/Home/Library/Java/JavaVirtualMachines/Versions/<Java Version>/Home/Library/Java/JavaVirtualMachines/<Java Version>/Contents/Home
Defining Custom directory to Search for Java
You can define a custom directory on an agent to search for Java installations in by adding the teamcity.agent.java.search.path property to the buildAgent.properties file.
You can define a list of directories separated by an OS-dependent character.
Defining Java-related Environment Variables
For each version of Java, the following variable is defined: JDK_<major>_<minor>[_x64]. For example, env.JDK_1_6 (Java 6) or env.JDK_14_0_x64 (Java 14 64-bit).
The JDK variables are defined when the JDK is found. Before Java 11, the JRE variables are defined when the JRE is found but the JDK is not.
The _x64 variables point to 64-bit Java only; the variables without the _x64 suffix may point to both 32-bit or 64-bit installations but 32-bit ones are preferred.
If several installations with the same major version and the same bitness but different minor version/update are found, the latest one is selected.
In addition, the following variables are defined:
JAVA_HOME— for the latest JDK installation (but 32-bit one is preferred)JDK_HOME— the same asJAVA_HOMEJRE_HOME— for the latest JRE or JDK installation (but 32-bit one is preferred), defined even if JDK is found
The JRE_HOME and JDK_HOME variables may points to different installations; for example, if JRE 1.7 and JDK 1.6 but no JDK 1.7 installed — JRE_HOME will point to JRE 1.7 and JDK_HOME will point to JDK 1.6.
All variables point to the Java home directories, not to binary files. For example, if you want to execute javac version 1.6, you can use the following path:
In a TeamCity build configuration:
In a Windows bat/cmd file:
In a Unix shell script:
Agent Build Properties
These properties are unique for each build: they are calculated on the agent right before build start and are then passed to the build.
System Property Name | Environment Variable Name | Description |
|---|---|---|
| none | Checkout directory used for the build. |
| none | Working directory where the build is started. This is a path where TeamCity build runner is supposed to start a process. This is a runner-specific property, thus it has different value for each new step. |
| none | Full path of the build temp directory automatically generated by TeamCity. The directory will be cleaned after the build. |
|
| Full name (including the path) of the file containing all the |
| none | Full path to a file with information about changed files included in the build. This property is useful if you want to support running of new and modified tests in your tests runner. This file is only available if there were changes in the build; it is not available for history builds. |
See also system properties related to Risk Tests Reordering in Custom Test Runner.