JetBrains TeamCity Blog

In the upcoming TeamCity 5.1 we’ve added an often requested feature – artifact packaging.

As you probably already know, in TeamCity you can easily configure artifact upload to the server. Later, from a build page, you can download all artifacts of the build. You can specify both directories and individual files as artifacts. The syntax for this is rather simple.

Build artifacts enable another really popular feature – custom reports. The essence of the feature is that if your build produces a report, viewable in a browser (any HTML/Text/Image/PDF), you can integrate this build report into the TeamCity interface. Report files are sent to TeamCity as artifacts, and you configure the report view in the TeamCity UI. One of the interesting things about custom reporting is that TeamCity can extract individual report files from ZIP-packaged archives. So if your report is a big directory with hundreds of files, you better zip them first before sending (to speedup the upload process).

Before TeamCity 5.1, you needed to zip the files in your build script. This required writing an Ant or NAnt task which prepared corresponding archive file. Unfortunately, not all build runners allow creating zip files.

In TeamCity 5.1, artifacts can be packed without modification of your build scripts. Just use archive suffix in your target path, and that’s it:

  testng-report => testng.zip
  **/src/**/*.java => sources/all-java-files.tgz

You can use suffixes zip, jar, war, tgz, tar.gz to specify type of the archive. For jar and war archives, the file format is just zip.

And as you would have expected, if you use tar/gz packaging on a UNIX system, TeamCity preserves file mode of the files, username, and group.

You can try artifact packaging in the just opened TeamCity 5.1 EAP builds.

Hope you’ll like these bits of syntax-sugar, and please share your feedback!

We are glad to announce, that we’ve just opened an Early Access Program for TeamCity 5.1.

Here’s the short list of only some of the improvements and features that today’s EAP brings:

• Customizable email notifications — now you can use FreeMarker templates to create your custom notification messages.
• Several UI improvements, such as collapsible projects on overview page and the most voted one — the ability to specify time zone, which is handy for geographically dispersed teams.
• New Current problems tab is added for a project, that shows which tests are currently failing in this project and which configurations are red.
• Support for .NET 4.0, and not yet released Visual Studio 2010 and TFS 2010.
• Improved support for .NET test frameworks.
• Code coverage support for Maven runner.
• Ability to produce zip and tar.gz artifacts from a bunch of files.
• IDE integration plugins improved.
• read more…

View the detailed release notes, download the build and stay tuned — TeamCity 5.1 won’t take long to appear.

By tradition, we remind you to back up your data before upgrade.

Looking forward to your feedback!

Sincerely,
JetBrains TeamCity team.

If you have ever dealt with .NET code coverage for NUnit tests, you surely know that it is quite a tricky thing to configure: you need to read docs to properly set up launching a command line coverage tool in your build script; read more docs and configure how reports should be gathered; then read docs again and specify all the needed arguments to be passed… well, not a task anyone would like to deal with.

Now imagine that you can forget all that tangled routine and spend more time doing whatever you like. That’s because starting with TeamCity 5.0 configuring coverage execution with NUnit becomes easy as pie.

All you need to do is to select the preferred coverage tool when creating or editing Build Configuration — NCover and PartCover are at your disposal; and specify its parameters. That’s it!

Just a few clicks to make TeamCity automatically add necessary arguments to NUnit tests, and ensure you’ll be able to view the results in the TeamCity. Enjoy!

Code Coverage Results

Code Coverage Summary

Coverage Graph

Sincerely,
JetBrains TeamCity team.

Technorati tags: TeamCity, JetBrains, continuous integration, build management, NCover, PartCover, NUnit, agile development

Great news for all TeamCity users!
We are glad to announce the fresh from the oven update – TeamCity 5.0.2, which brings a number of fixes you might find tasty.

Check the release notes for the complete list of included changes and download the build.
As usual, we recommend backing up your TeamCity data before upgrading to a new version.

Looking forward to your feedback!
Sincerely,
JetBrains TeamCity team.

Technorati tags: TeamCity, JetBrains, continuous integration, build management, agile development