TeamCity Versioning Changes

Since 2017, TeamCity adopts the common JetBrains versioning scheme that identifies versions by year, following the pattern: “<year>.<number of the feature release within the year>.<bugfix update number>”. Hence, we’ll be releasing TeamCity 2017.1, formerly known as TeamCity 10.1.

TFS Integration Improvements

TeamCity improves its integrations with VCS hosting services and now TeamCity can be connected to TFS/VSTS the same way it is connected to GitHub, GitHub Enterprise or BitBucket Cloud. Once a connection is configured, it is really simple to setup projects which use TFS/VSTS repositories.

TFS connections support Personal Access Tokens (on-premises, hosted) for TFS 2017+/VSTS

Maven and dotCover Installation on Agents

Now, in addition to the previously available ability to install Sysinternals handle.exe, Sysinternals psexec.exe, NuGet.exe and JetBrains ReSharper Command Line Tools,  you can easily distribute to/ remove from all agents different versions of the JetBrains dotCover Command Line Tools and Maven centrally using the Administration | Tools page.

Build Failure Conditions


Cloud Agents

Project level (?)

Tagging instance-dependent Amazon EC2 resources

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.

Partial Build Log Display

When opening large build logs, TeamCity now displays a part of it to avoid browser hanging. The configurable display threshold is set to 20M characters by default. You can view the full build log on clicking the corresponding link.

Faster Server Startup

During the server startup, several time consuming actions are now performed in parallel; in addition to that, the server warms up pages for faster display.

Web UI improvements

In this EAP, the following pages of the TeamCity Web UI were redesigned:

Build Chains Page

Enforce clean checkout  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.

The option also enables rebuilding all dependencies (unless custom dependencies are provided via the custom build dialog or  the schedule trigger promotes a build).

Other Improvements