Starting with this EAP we introduce another major feature of TeamCity 5.0: build configuration templates. Templates goal is to remove duplication from the build configuration settings. To do so you create a template (template actually has the same settings as regular build configuration) and then associate any number of build configuration with this template. After that, change in a template will affect all build configurations associated with it.
Note that most of the template settings can later be redefined in the build configuration with help of
configuration parameters. For example if you want to redefine Ant build targets in build configurations you can specify %ant.targets% in the corresponding field in the template, and then define custom value for this parameter in the build configuration. You can also add additional requirements and system/environment properties.
There are some limitations though. You can't redefine dependencies or VCS roots inherited from the template. Although you can use parameters in checkout rules. For example, with subversion you can have a VCS root for the root of the subversion repository associated with a template. And a parameter %checkout.rules% defined in the template checkout rules. Then in the build configuration you can specify
checkour.rules = +:trunk => . or
checkour.rules = +:release2_0 => .