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. Change in the template will affect all of the build configurations associated with it.
Edit template UI (note that UI is almost the same as for regular build configuration):
Edit build configuration inherited from the template:
Note that most of the fields except name and build counter are disabled. If build configuration is associated with template then settings of this build configuration can be edited in the template only. However it is possible to use
%param.name% syntax in the template text fields. And actual values for
param.name parameter can be provided in the build configuration itself. You can also add additional requirements and system properties or environment variables. Thus the settings redefinition works.
At the moment 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 add to the template a VCS root for the root of the subversion repository. Then in the template checkout rules you can write:
%checkout.rules%. Such setup will allow you to checkout trunk or branch in the specific build configuration and avoid settings duplication, i.e. in the build configuration you can specify
checkour.rules = +:trunk => . or
checkour.rules = +:release2_0 => .
Now Amazon cloud profiles can be edited from the web UI, there is no need to edit configuration files anymore.
We want to reduce time needed by a developer to discover which tests fail and why. In previous EAP builds we introduced change details page, now we decided to improve My Changes page in the similar way. Starting from this EAP you can see not only builds running with your change but also new tests already failed in these builds.
We added new kind of dependency trigger in this EAP: Maven artifact. This trigger will start a build if specified Maven artifact changes.