What's New in TeamCity 4.5

User Groups

A new concept, introduced in TeamCity, is User Group. A user can be included into one or several User Groups from Administration web UI. A predefined "All Users" group contains all users registered in the system and its members cannot be modified.

A group can have assigned roles and notification rules.

A user gets all the roles:

assigned to him or her directly.
assigned to the groups the user belongs to. These groups include the groups in which a user is both a direct and indirect member (indirect means user belongs to a group that itself belongs to another group).

A user gets all the notification rules from the groups he or she belongs to (both directly and indirectly) as defaul notification rules. All the user-configured notification rules have greater priority then groups-provided notification rules.

LDAP Integration

User Interface Improvements

Improvements of the Project page report tabs
Test Details and Problematic Tests display on a project level
Test List grouping
Improved integration of external change browser
Project-wide Change Log
Possibility to move the build on the top of the Build Queue when running custom build.
Possibility to rearrange the view of the Projects page: moving projects in the visible projects list.
Assigning responsibility for broken build
If a build failed because of failures in dependencies, actually failed dependent builds are shown on the Build Results page.
Indirect dependencies are displayed on the build Dependencies tab.
VCS roots page displays warnings on the VCS errors; the list of VCS roots is broken down into pages, and you can now find the desired root by typing its name and clicking the Filter button.
User can now leave a comment when pausing a build configuration.
Builds with "My changes" now have "Changes" block highlighted for better visibility.

Support of Mono framework

TeamCity .NET runners were made compatible with Mono Framework, so that it can now be used as a .NET platform for continuous builds. Also, Build Agents now attempt to automatically detect presence of Mono framework, and if it's installed, set system properties which you can use when specifying the build settings and Build Agent requirements.

IDE Integration Plugins Improvements

Eclipse

CVS is now supported for remote run and pre-tested commit.
Support for Perforce 2008.2 plugin.
Browse failed tests output without leaving IDE.

Microsoft Visual Studio

Perforce support.
Subversion 1.6 support.

IntelliJ IDEA

IntelliJ IDEA 8.1 is supported.

XML Reporter

Now TeamCity can process various XML reports and feed data to TeamCity. The following formats are supported:

Ant's JUnit task
NUnit
Surefire
PMD
FindBugs

You can now import XML test reports using the bundled XML Test Reporting plugin.

VCS Improvements

SVNKit library for Subversion support is updated.
TFS sources labeling is now supported. TFS checkout on agent is improved.

Other Improvements

Moving a build configuration to another project.
Possibility to download all build artifacts in a .zip archive.
Agents can be disabled with a timeout (useful when disabling an agent for current issue investigation).
JVM crashes and Java OutOfMemory errors are now detected, and a build summary is changed accordingly.
TeamCity server disk space watcher will notify if disk space available for artifacts and build logs is less than a threshold (10Mb).
Rebooting a Build Agent.
Build Agent checks for free space and ensures the old data is cleaned up before the build if the free space exceeds a particular amount.
NAnt runner supports specification of the target. framework (-targetframework: option).
MSTest 2005 is now supported (in addition to MSTest 2008).
TFS performance improvements
Taking thread dumps to build log on execution timeout.
Bundled Ant is updated to 1.7.1
Remote API is updated.

Previous Releases

What's New in TeamCity 4.0