The predefined properties can originate from several scopes:
There is also a special kind of server-side build properties that can be used in references while defining other properties, but are not passed into the build. See Reference-only Server Properties below for the listing of such properties.
These are the properties that other properties can reference (only if defined on Build Parameters page), but that are not passed to the build themselves.
The following sets of such properties exist:
Properties provided by the builds the current build depends on (via snapshot or artifact dependency).
Dependencies properties have the following format:
These are the settings of a VCS roots attached to the build configuration.
VCS properties have the following format:
If there is only one VCS root in a build configuration, <simplified VCS root name>. part can be omitted.
Properties marked by VCS support as secure (for example, passwords) are not available as reference properties.
For Git & Mercurial TeamCity provides additional parameters with names of VCS branches known at the moment of build starting. If a build took a revision from the refs/heads/bugfix branch, TeamCity will add a configuration parameter with the following name:
Where <simplified VCS root name> is the VCS root name as described above.
When TeamCity starts a build in configuration where Branch specification is configured it adds branch label to each build. This branch label is also available as configuration parameter:
TeamCity can start build in default and non-default branch, additional parameter available since 7.1.5 allows to distinguish these cases:
Agent-specific properties are defined on each build agent and vary depending on its environment. Aside from standard properties (for example, os.name or os.arch, etc. — these are provided by JVM running on 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 lack of some property) and inside build scripts. For more information on how to reference these properties see Defining and Using Build Parameters in Build Configuration page.
The actual properties defined on agent can be reviewed on the Agent Details page.
These properties are unique for each build: they are calculated on the agent right before build start and are then passed to the build.
Skip to end of metadata Go to start of metadata