MSBuild and Visul Studio Solution build runners now have full support for Microsoft® Visual Studio 2013 and Microsoft® Build Tools 2013. Support for the new version of Visual Studio in the TeamCity Add-in and MSTest build runner will be added in the future versions.
If you are using feature branches with Git and Mercurial, you can now configure TeamCity to merge a feature branch automatically to the master if a build in the feature branch completes successfully.
h2. Simple/advanced options on build configuration settings Build configuration and VCS root settings are divided into simple and advanced options.
A new build feature for VCS labeling was added. VCS labeling settings will be converted automatically to this build feature. The build feature allows more flexible configuration, you can now have different labeling settings for different VCS roots, or overwrite labeling settings inherited from a template completely.
In previous versions there were two places where you could configure report tabs:
Starting with version 8.1, both project and build report tabs are configured on the project level; thus project administrators can manage build report tabs themselves.
These settings have also been moved from the global administration area to the project level, the Maven Settings tab. This makes it possible to delegate configuring Maven settings to project administrators.
A new coverage engine based on JaCoCo is now available for Ant, Maven, Gradle and IDEA Project build steps.
You can now list targets/tasks, IntelliJ IDEA run configurations and inspection profiles right on the build step page.
For Java based runners, there is a Java selection drop down with versions of Java detected on available agents.
Some new health reports were added:
Additionally, some of the health reports that do not require administrator's permissions are now available in the user space, on the build configuration home page.