Advanced LDAP Integration

Another long-awaited feature — LDAP synchronization — enables TeamCity to retrieve user profiles and group memberships from your company's directory, and to keep them synchronized with the LDAP server. There's also an option to automatically create or remove user accounts once they are found in the associated LDAP group.

Better Insight

TeamCity 4.5 comes with many usability improvements. One of the most important is the ability to group build test results by suites, packages/namespaces and classes. Once you reach the limit of tens of thousands tests in a project, this feature becomes a godsend. Other considerable improvements over version 4.0: Test Details, Problematic Tests and Change Log have now become available at the project level. This gives much better access to all project-related information, and also allows you to catch problems by comparing different build configurations.

Improved IDE and VCS integrations

All TeamCity IDE plugins have been updated to increase their stability and compatibility. The Eclipse plugin adds support for remote run and pre-tested commits with CVS, and compatibility with Perforce 2008.2. The Visual Studio plugin also introduces support for Perforce.

One more thing, we're planning to add support for Git in the TeamCity server. It's in EAP, and can now be downloaded separately as a plugin.

XML Reports Handling

From the day one TeamCity has been using sophisticated mechanisms to intercept testing tool outputs in order to provide real-time test results rendering, a unique TeamCity feature not found in any other CI system. This did, however, require a decent knowledge about the internals of all supported building tools, and sometimes led to compatibility problems with different versions or different flavors of the same tool. TeamCity 4.5 solves those problems. In addition to real-time handling, TeamCity is now able to parse raw XML reports from ANT's JUnit tasks, NUnit, Surefire, PMD, and FindBugs. This provides a fallback for getting reports in case of compatibility issues.

Mono Framework

TeamCity .NET runners are now compatible with the Mono Framework, allowing you to use Mono as your .NET platform on build agents for continuous builds. Also, build agents now automatically detect the presence of Mono in a system, so you can specify it in the build settings and build agent requirements.

More TeamCity 4.5 improvements

• Assign responsibility. In addition to taking over responsibility for a broken build, you can now assign it to another person and get an automatic notification
• Movable build configurations. You can now move build configurations from one project to another, keeping all build history and statistics
• Download build artifacts as Zip. There's now an option to download all build artifacts as a .zip archive. This can save you a bunch of extra clicks
• JVM crashes detection. If a JVM crash or Java OutOfMemory error occurs during your build, they are automatically detected, and the build summary is changed accordingly
• Improved agent management. Now you can remotely reboot a build agent machine, as well as disable an agent for a specified period of time (provided you have permission to do so)