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. 

 

Visual Studio Team Services Connection

TeamCity improves its integrations with VCS hosting services and now TeamCity can be connected to 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 VSTS repositories.

Installing dotCover Centrally on Agents

Now you can easily distribute to/ remove from all agents different versions of the JetBrains dotCover Command Line Tools centrally using the Administration | Tools page. The page displays the installed versions, the dotCover CLT usages in build configurations. The bundled version is set as default. You can install other versions and change the defaults. 

Installing Maven Centrally on Agents

Now you can easily distribute to/ remove from all agents different versions of Maven centrally using the Administration | Tools page. The page displays all the bundled versions of Maven, with one set as default. You can install the version you need and change the default Maven version for all agents.

Build Failure Conditions

REST API

Cloud Agents

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 7M 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:


Enforce clean checkout for build chain

A new option in the schedule trigger and the custom run dialogue allows 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