The user interface update that we started in the previous version continues in the future 2018.1 version.
In this EAP build, the build line has been redesigned a bit and the agent history page now looks similar to "the All builds Builds page " (which was introduced in 2017.2.x):
Starting with this EAP it is now possible , TeamCity provides the ability to enforce settings for all of the build configurations in a projects project hierarchy. For instance, with help of this feature it is possible to enforce agent side checkout everywhere, or make sure that all build configurations have some strict execution timeout.
To enforce some settings in the projects project hierarchy, a template with these settings must be created. After that, a system administrator can set this template as the enforced settings template in a the project:
To some extent, the enforced settings template works similar similarly to the default templates template - i.e. all of it's settings are inherited in build configurations of a projects the project hierarchy. The difference is that these inherited settings cannot be disabled or overridden anyhow. In addition to that, only system administrator can associate a project with a specific enforced settings template . It's not enough to be a project administrator to do that- project administrator permissions are not suffieicient. On the other hand, the template itself can be edited by a project administrator who can administer the project where the template is defined.
If the enforced settings template is specified in a project and another template is assigned as the enforced settings in a subproject, then for this the subproject it's template will have the higher priority.
Limitations: not all of the settings can be enforced. Dependencies, triggers, and build steps are currently not enforced. We're not convinced there are useful use cases for them, please let us know if you have some cases in mind.