|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 Template allows you to eliminate duplication of build configuration settings. If you want to have several similar (not necessarily identical) build configurations and be able to modify their common settings in one place without having to edit each configuration, create a build configuration template with those settings. Modifying template's settings affects all build configurations associated with this template.
When you associate an existing build configuration with template, it inherits all settings defined in template, and if there's a conflict, template settings supersede the settings of build configuration (except dependencies, parameters and requirements).
Although a build configuration associated with a template inherits all it's settings, it is still possible to fine tune the some of the inherited settings: you can extend the set of inherited settings or redefine some of them.
Text field settings
Other settings: drop-downs, lists, check boxes, etc.
Refer to Configuring Build Parameters for more details on redefining settings.
When you detach build configuration from a template, all settings from the template will be copied to the build configuration and enabled for editing.
Template which has at least one associated build configuration cannot be deleted.