|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.|
Build 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 home page and modify its settings on the editing page. In this section:
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 automatic 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 My Changes page.
To pause or activate a build configuration do one of the following:
In general, build configuration status reflects the status of its last finished build.
You can view the build configuration status on the Projects page or Project Home Page, when the details are collapsed.
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: