Gaya 8.1 EAP2 (build 29581) Release Notes

Skip to end of metadata
Go to start of metadata

Administration UI improvements

Navigation

Project and build configuration editing pages have been reworked for better consistency:

  • the project tab navigation changed to the vertical layout to be more consistent with the general Administration page
  • the navigation sidebar inside build configuration pages has been moved to the left for consistency as well
  • the Actions drop-down in the upper right corner has replaced the menu with options to copy, move, etc. a project or build configuration

Auto-Discovery

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.

Duplicate VCS roots detection

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:

Data directory browser

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.

External database set-up on the TeamCity start

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.

Build failure conditions

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).

REST API

Several new features were added in TeamCity REST API. It can now be used to:

  • trigger a build
  • list builds in the build queue
  • stop a running build
  • access the canceled build details
  • query for investigations for a build problems and tests in addition to build configuration investigation
  • list investigations assigned for a user
  • list the build's tests
  • get test run history
  • delete a build agent
  • assign project to an agent pool

Visual Studio 2013

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.

Statistics

All statistic values published by a specific build are now available on the Build Parameters tab:

Other Improvements

  • the bundled dotCover has been updated to version 2.6
  • TeamCity now supports Xcode 5
  • Subversion 1.8 is now supported on the server and on the agent, support in Eclipse is on the way
  • health reports are now available for Maven runner configurations
  • you can now reset the build history clean-up rules to the defaults.
  • all artifacts published by a build are now cached in the local artifact dependencies cache on an agent, this should speedup artifact dependencies in some cases
  • TeamCity now fully supports Maven 3 projects, see TW-22984 and related requests
  • complete list of fixed issues
Labels:
None
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.