Build Configuration
Last modified: 20 April 2023Build Configuration describes a class of builds of a particular type, or a procedure used to create builds. Examples of build configurations are integration builds, release builds, nightly builds, and others.
You can explore details of a build configuration on its Build Configuration Home Page and modify its settings on the Creating and Editing Build Configurations. In this section:
Build Configuration State
A build configuration is characterized with its state which can be paused or active. By default, when created all configurations are active.
If a build configuration is paused, its Configuring Build Triggers are disabled until the configuration is activated. Still, you can start a build of a paused configuration manually or automatically as a part of a build chain. Besides, information on paused build configurations is not displayed on the Viewing Changes page.
To pause or activate a build configuration do one of the following:
On the Build Configuration settings page click the Pause/Activate button.
Navigate to the Build Configuration Home Page, click Actions on the toolbar and select Pause build configuration/Activate build configuration from the drop-down.
Build Configuration Status
In general, build configuration status reflects the status of its last finished build.
note
Personal Build do not affect the build configuration state.
You can view the build configuration status on the Projects page, Project Home Page, or in the title of the build configuration home page.
Icon | Build configuration status | Description |
---|---|---|
successful | The last build executed successfully. | |
failed | The last build with this build configuration executed with errors or one of the currently running builds is failing. The build configuration status will change to "failed" when there's at least one currently running and failing build, even if the last finished build was successful. | |
responsibility taken | Some developer is trying to fix the problems with the failed builds (see Assigning Responsibility for Build Problem). | |
probably fixed | The developer who took responsibility for the failed builds has submitted a fix; in this case the status will not change to successful until the build with the fix has executed successfully. | |
unknown | There were no finished builds in this configuration. | |
paused | The build configuration is paused; no builds are triggered for it. |
Build Configuration ID
Each build configuration has an internal unique identifier which you may need when constructing TeamCity URLs or editing TeamCity configuration manually.
Automatically assigned IDs use bt<NUMBER>
format.
To determine the internal ID of a build configuration:
Navigate to the build configuration home page and in page URL, find the
buildTypeID=btXXX
parameter (see picture below). ThebtXXX
value is the value you search for.

Thanks for your feedback!