TeamCity 5.1 is finally here, so don’t hesitate to download and try it. The majority of the features included in this release might be familiar to you already from EAP builds and our blog posts. Let’s summarize what we’ve got for you:
- Notifications: Brushed up notification templates are now based on Freemarker, which provides great customization abilities. Also, Email notifier now uses HTML for email messages.
- Build triggers: Build triggers were reworked – now you can add triggers and VCS roots to the build configurations inherited from a template. Additionally, build triggers UI has become more convenient.
- Code coverage in Maven runner: code coverage based on IDEA coverage engine is now available for those who use Maven runner.
- Time zone detection: you can enable time zone auto-detection, which is handy for geographically dispersed teams.
- Enhanced .NET support:
- Added support for .NET 4.0, Visual Studio 2010 and TFS 2010.
- All solution runners (except 2003) were merged into Visual Studio (sln) runner, which includes support for Visual Studio 2010.
- NUnit tests UI is available in MSBuild runner.
- NAnt 0.90 alpha 1 is supported.
- Added support for NUnit 2.5.3 and 2.5.4.
- Improved .NET Coverage reporting
- and more.
- Artifacts publishing: TeamCity agent now is able to produce zip and tar.gz artifacts from a bunch of files and upload the resulting archives to the server.
- Java detection on agents: New plugin for agent detects installed Java (JDK and JRE) and sets corresponding environment variables.
- Improved IDE integration: remote run with custom properties or environment variables available in all IDE integration plugins, plus each plugin contains new features.
- Moreover multiple UI improvements, new tabs, actions, filters and a bunch of features – this release contains more than 500 various improvements.
Take a look at the What’s New page for more details and download TeamCity 5.1.
By the way, now upgrade has become easier – you still need to make a backup, but since TeamCity 5.1 you can store your jdbc jars under the TEAMCITY_DATA_PATH/lib/jdbc directory – hopefully this will save you some time.
The JetBrains TeamCity Team