Unable to render embedded object: File (TeamCity48.png) not found.

TeamCity 10.x and 2017.x Documentation

Icon

You are viewing the documentation of TeamCity 10.x and 2017.x, which is not the most recently released version of TeamCity.
View this page in the latest documentation or refer to the listing to choose the documentation corresponding to your TeamCity version.

 

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

System Property Name

Environment Variable Name

Description

teamcity.version

TEAMCITY_VERSION

The version of TeamCity server. This property can be used to determine the build is run within TeamCity.

teamcity.projectName

TEAMCITY_PROJECT_NAME

The name of the project the current build belongs to.

teamcity.buildConfName

TEAMCITY_BUILDCONF_NAME

The name of the Build Configuration the current build belongs to.

teamcity.buildType.idnoneThe unique id used by TeamCity to reference the Build Configuration the current build belongs to

teamcity.configuration.properties.file

noneFull name (including path) of the file containing all the build properties in alphabetical order.
 build.is.personal

BUILD_IS_PERSONAL

Is set to true if the build is a personal one. Is not defined otherwise.

Anchor
buildNumber
buildNumber
build.number

BUILD_NUMBER

The build number assigned to the build by TeamCity using the build number format. The property is assigned based on the build number format.

teamcity.build.id

none

The internal unique id used by TeamCity to reference builds.

teamcity.auth.userId

none

A generated username that can be used to download artifacts of other build configurations. Valid only during the build. Details

teamcity.auth.password

none

A generated password that can be used to download artifacts of other build configurations. Valid only during the build. Details 

Anchor
build_vcs_number
build_vcs_number
build.vcs.number.<VCS root ID>

BUILD_VCS_NUMBER_<VCS root ID>

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 build.vcs.number property (without the VCS root ID) is also provided.

Note

Please note that this value is a VCS-specific (for example, for SVN the value is a revision number while for CVS it is a timestamp)

hidden-data
In versions of TeamCity prior to 4.0, a different format for the VCS revision number when specified in a build number pattern was used: {build.vcs.number.N} where N is the VCS root order number in the build configuration. If you still need this to work, you can launch TeamCity with a special [internal option
:

Code Block
|Configuring TeamCity Server Startup Properties]:
{code}
teamcity.buildVcsNumberCompatibilityMode=true
{code}

Configuration Parameters

Anchor
Reference-only Server Properties
Reference-only Server Properties
Wiki Markup
{show-if:mode=edit} These properties are available only *since TeamCity 4.5*. In TeamCity 4.0.x you could only use [#Dependencies Properties] in the build number and VCS labeling pattern.{show-if}
These are the parameters that other properties can reference (only if defined on the Parameters page), but that are not passed to the build themselves.
Anchor
get_listing_of__reference_only_properties
get_listing_of__reference_only_properties

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.

...