|You are viewing documentation of TeamCity 6.5.x, which is not the most recent released version of TeamCity. Please refer to the listing to choose another version.|
To learn about build parameters in TeamCity, please refer to the Configuring Build Parameters page.
Defining Build Parameters in Build Configuration
On the Build Parameters page of Build Configuration settings you can define required system properties and environment variables to be passed to the build script and environment when a build is started. Note, that you can redefine them when launching a Custom Build.
Build Parameters defined in Build Configuration are used only within this configuration. For other ways, refer to Project and Agent Level Build Parameters.
Any user-defined build parameter (system property or environment variable)can reference other parameters by using the following format:
Using Build Parameters in Build Configuration Settings
In most Build Configuration settings you can use a reference to a Build Parameter instead of using actual value. Before starting a build, TeamCity resolves all references with available parameters. If there are references that cannot be resolved, they are left as is and a warning will appear in the build log.
To make a reference to a build parameter use:
Any text appearing between percentage signs is considered a reference to a property by TeamCity. If the property cannot be found in the build configuration, the reference becomes an
Where References Can Be Used
If you reference a build parameter in a build configuration, and it is not defined there, it becomes an agent requirement for the configuration. The build configuration will be run only on agents that have this property defined.
Using Build Parameters in VCS Labeling Pattern and Build Number
In Build number pattern and VCS labeling pattern you can use
Using System Properties in Build Scripts
Any system property (
To get the file names that store the full set of properties, use can use