- When launching Amazon EC2 instances, TeamCity now tags all the resources (e.g. volumes and network adapters) associated with the created instances, which is important when evaluating the overall cost of an instance (taking into account the storage drive type and size, I/O operations (for standard drives), network (transfers out), etc.
Agent Could Cloud profile configuration has been moved from the server level to the Root project level. In 2017.1 we intend to move cloud agent profiles to the project level, to allow Project administrators to configure their own cloud profiles without bothering System administrators.
If you use Kotlin DSL for your TeamCity Root project settings, make sure you update your DSL as described below.
Update Root Project DSL Settings with Cloud Profiles
Cloud profiles were moved from the server level to the Root project level, which means you can now use Kotlin DSL to define your cloud profiles.
If you had cloud profiles previously configured and you use Kotlin DSL for the Root project settings, the cloud profiles information will be lost unless you update your DSL.
To update your settings with the cloud profile information, perform the following:
- Run the Download settings in Kotlin format action in the Root project and save the zip with the generated DSL
- Copy project features of type
.teamcity/_Root/Project.ktfile to the root project config in your settings
- Commit your changes to the VCS.
Enable versioned settings on the Versioned Settings tab of the Root project.
the login page, register user, administrator setup, and startup pages have been revised
the Create Project / Build Configuration pages were renewed
The Build Chains tab now:
provides a more compact representation of chains. Previously, if several top builds triggered the same chain of dependent builds, TeamCity displayed several build chains. Now only one build chain is displayed with several “top builds”.
has additional display options: “Group by projects”, “Hide details”, and “Hide redundant edges”.
transitively highlights all the downstream/upstream builds when a build is selected in a build chain.
Enforce clean checkout for for build chain
A new option in the schedule trigger and the custom run dialogue allowing you to clean all files in the checkout directory before a build. If applied to snapshot dependencies, all the builds of the build chain will be forced to use clean checkout.