JetBrains TeamCity Blog

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

In the previous post about .NET coverage, we’ve told about configuring NCover/PartCover settings right in the web UI. This solution suits perfectly well for those, who use MSBuild, NAnt or Visual Studio (sln) runner. However, since version 5.1, you can get the coverage results displayed in TeamCity, even if you use a runner other than listed above.
If your build produces coverage report .xml files, you can populate your build script with simple service messages – and voila! TeamCity will merge those coverage reports, publish statistics and generate html-report for you.

Start with configuring TeamCity .NET Coverage reporting parameters in your build:

##teamcity[dotNetCoverage key='value']

where key is a .NET Coverage reporting parameter (the complete list of the values can be found in our docs).  Make sure to set up all parameters before reporting coverage .xml files.

Now, to pass generated coverage .xml files to TeamCity, use the following service message:

##teamcity[importData type='dotNetCoverage' tool='<tool name>' path='<path to the results file>']

where tool name can be partcover, ncover or ncover3. Hope, you’ll find it useful.

Stay tuned for TeamCity 5.1!

Sincerely, The JetBrains TeamCity team

While TeamCity 5.1 is almost at your doorstep, we have published another release candidate build with a number of fixes in it.
Besides, this build comes with bundled SourceGear Vault plugin – try it and give us feedback on it.

At this point we keep polishing the build, and the wait hopefully will be over soon, so stay tuned!

As usual, do not forget to backup your data before upgrading.
The JetBrains TeamCity Team

Today’s TeamCity 5.1 EAP build is quite special, because it has a Release Candidate status. We have frozen feature development and focused on fixes and general polishing now. So your feedback is even more appreciated – you can help us discover critical issues and make our beloved TeamCity even better.

Stay tuned for TeamCity 5.1!
Before upgrading, do not forget to back up your current data.

Sincerely,
The JetBrains TeamCity Team

New TeamCity 5.1 EAP build is available, which brings several noteworthy improvements and contains a lot of bug-fixes. The major improvement concerns build triggers:

• Starting with this EAP, you can enble/add triggers to build configurations based on a template, which previously was not possible. Additionally, build triggers UI has become more convenient.
  
• Moreover, build triggers are now pluggable, i.e. it is possible to add custom build trigger with custom web UI, read more.

Plus, there are several other improvements you might find interesting:

• Ability to run personal build with custom parameters from Eclipse plugin.
• Support for NAnt 0.90 alpha 1.
• Same archive name can be specified multiple times in the right part of the artifacts settings, i.e.:
  **/*.html => report.zip
**/*.css => report.zip!/css/
• Improved notification templates.

Take a look at the release notes, check the complete list of changes, and try the build. Just to be on a safe side, do not forget to back up your data before upgrade.

As usual, feedback is appreciated.
The JetBrains TeamCity Team