Project and build configuration editing pages have been reworked for better consistency:
We added a new auto-discovery feature enabling TeamCity to determine the type of VCS and settings from the repository URL:
At the moment TeamCity recognizes URLs for Subversion, Git and Mercurial. TFS and Perforce are partially supported.
Auto-discovery of build steps has been significantly improved. TeamCity now detects Ant, NAnt, Gradle, Maven, MSBuild, Visual Studio solution files, Powershell, Xcode project files, Rake and IntelliJ IDEA projects.
The new auto-suggestion feature which works for triggers, failure conditions and build features, makes creating a build configuration a lot easier. Depending on the build configuration settings, it can suggest some additional configuration options.
On an attempt to create a new VCS root, TeamCity checks whether there are other VCS roots accessible in this project with similar settings, and if such VCS roots exist, suggests using them instead of creating a new one:
You can browse TeamCity Data Directory right from the web interface. It is also possible to upload new files into the data directory and modify the existing files.
You can now setup TeamCity to use an external database right on the server start-up: all you need to do is select the type of the database and specify database connection settings. You may also need to download the JDBC driver for you database.
A build failure condition on a metric change has been extended with the support for percentage. You can now fail a build if the number of tests is, for example, 10% lower than in some other build. We have also redesigned the web interface to make it more straightforward:
Finally, there is one more metric for passed tests (in addition to ignored, failed and total).
Several new features were added in TeamCity REST API. It can now be used to:
This EAP comes with VS addin compatible with Visual Studio 2013. We also updated .NET Command line tools, so now .NET Inspections and Duplicates runners can work with latest solution files.
Additionally, support for MSTest 2013 (12.0) has been added.
All statistic values published by a specific build are now available on the Build Parameters tab: