JetBrains TeamCity Blog

Truly great news, everyone! Today we announce the opening of TeamCity 5.0 Early Access Program.

We’ve been working hard and we believe it’s time to present you some of TeamCity’s brand new features and enhancements to make your day a bit brighter.
So here goes a brief list of what you’ll find in this first TeamCity 5.0 EAP:

• Issue Tracker integration — out-of-the-box integration with JIRA, Bugzilla, and Charisma (it’s a new issue tracker by JetBrains)
• New code coverage engine for Java — IntelliJ IDEA built-in coverage
• Built-in support for seamless integration with NCover and PartCover for .NET coverage
• Single page to monitor status of a particular change across all of the build configurations
• Customizable UI for artifact-based (report) tabs
• Archived Projects — one click to sort out non-active projects
• Audit and Server logs — let you browse various users activity and server events via web UI
• Eclipse and Visual Studio IDE plug-ins improvements
• Enhanced Rake Runner with new test frameworks support
• Experimental support for Sybase DB engine
• and more niceties…

Quite a list, don’t you think? Just give these features a try, and, who knows?, you might get a taste for them!
If you’d like to get more information and try new features, view detailed Release notes and download the build. Of course, we remind you to back up your data before upgrade.

By the way, don’t hesitate and take a chance to influence the development process — vote for features and suggest new ones at our issue tracker and online forum. We greatly appreciate and eagerly wait for your feedback!

Wish you happy building!
The JetBrains TeamCity team

Technorati tags: TeamCity, JetBrains, IntelliJ IDEA, Eclipse, continuous integration, build management, EAP, early access program, agile development, Visual Studio, Issue tracker integration, Sybase, NCover, PartCover, Code coverage

Today’s piping hot TeamCity 4.5.4 update eliminates several compatibility problems and increases overall stability. For the complete list of included fixes, check Release Notes. This update is recommended for all users of TeamCity.

TeamCity 4.5.4 is available for download now. As usual, we do recommend you to back up your data before upgrade.

Wishing you develop with pleasure!
The JetBrains TeamCity team

Technorati tags: TeamCity, pre-tested commit, personal build, remote run, JetBrains, IntelliJ IDEA, Eclipse, continuous integration, build management, agile development, Git, FishEye, MS Visual Studio 2005, MS Visual Studio 2008

We’re glad to announce the fresh update – TeamCity 4.5.3, which solves a Rake Runner problem introduced in TeamCity 4.5.2 and contains a few more fixes.
For the complete list of included changes, check Release notes.

Download TeamCity 4.5.3 and, please, don’t forger to back up your data before upgrading.

Wishing you develop with pleasure and waiting for your feedback!
The JetBrains TeamCity team

Technorati tags: TeamCity, JetBrains, Rake, Ruby, Subversion, FxCop, MS Visual Studio 2005, MS Visual Studio 2008, pre-tested commit, personal build, remote run, continuous integration, build management, agile development

We’re glad to inform you that TeamCity 4.5.2 is just released. This fresh update comprises bundled SVNKit 1.3 support and a number of fixes. For the complete list of included changes check the Release notes.

You are welcome to download the new version from our official site, and, please, don’t forger to back up your data before upgrading.

This update is recommended for all users of TeamCity Professional and TeamCity Enterprise editions.

Wishing you develop with pleasure and waiting for your feedback!
The JetBrains TeamCity team

Technorati tags: TeamCity, pre-tested commit, personal build, remote run, JetBrains, IntelliJ IDEA, Eclipse, continuous integration, build management, agile development, Git, FishEye, MS Visual Studio 2005, MS Visual Studio 2008

As you probably know, it’s been about a year now since TeamCity migrated from Jira to an in-house issue tracker, code-named Charisma.

Those of you who have ever posted any requests to our tracker have probably got used to its features and GUI. However, one year is a heck of long time, and of course Charisma did evolve since then. The time for change has come, and a week ago the brand new UI has been pushed to www.jetbrains.net/tracker, and now you can try it yourself. The old-timey UI (aka “workspace”) will be abandoned soon.
So head to your profile (“Settings” tab) in the tracker and select “Use New UI”. You will then be redirected to the new UI URL: www.jetbrains.net/tracker/issues.

You can still reach the old UI at www.jetbrains.net/tracker/oldWorkspace, but if you ever need it — let us know why. We are eagerly waiting for your feedback: we’d like to improve the new UI so that you feel comfortable using it, before we drop the old one for good.

Please, don’t hesitate to share your opinion, ideas and suggestions with us in TeamCity community. If you have found a bug, post the issue right into Charisma.

We wish you happy building with TeamCity and hope to hear from you soon!
The JetBrains TeamCity Team

Technorati tags: TeamCity, Charisma, continuous integration, issue tracker, build management, agile development, JetBrains, IntelliJ IDEA, Eclipse, MS Visual Studio 2005, MS Visual Studio 2008, Mono

Now TeamCity is equipped with a new feature designed to improve your project ROI and raise team motivation. It allows you to automatically charge developers for broken builds, abusing hardware resources, and more.
 
The charging feature provides a web UI where administrators can customize conversion rates and charging rules, as well as the list of accepted credit cards and payment methods.
 
To start improving your project bottom-line today, click here to learn more and download the latest TeamCity build.
 
As always, we are eager to hear your feedback. We also recommend backing up your data before you upgrade.
 
Enjoy your profitable building!
 
The JetBrains Team

Technorati tags: TeamCity, continuous integration, build management, agile development, JetBrains, IntelliJ IDEA, Eclipse, MS Visual Studio 2005, MS Visual Studio 2008, Mono

Good day, dear friends!
TeamCity 4.0 release is getting one step closer to you – we've published TeamCity 4.0 Release Candidate!

Compared to previous EAP, this RC is basically about bug fixing plus a bit of enhancements.

So, don't hesitate and download TeamCity 4.0 RC, and, of course, do not forget to backup your TeamCity data before upgrading!
As always, your feedback is highly appreciated!

Stay tuned, for the release is just around the corner!
The JetBrains TeamCity Team

Technorati tags: TeamCity, pre-tested commit, JetBrains, IntelliJ IDEA, Eclipse, continuous integration, build management, agile development, MS Visual Studio 2005, MS Visual Studio 2008

After not so short break we are back with the next post of our .NET mini-series, and today we are going to tell you about TeamCity NUnit Launcher — a bundled NUnit test runner. In most cases, if you need to use NUnit, all you have to do is just to run it with this Launcher.

As we said in the previous post, to provide tests state tracking and on-the-fly reporting, TeamCity contains several NUnit builds (different NUnit versions) and provides NUnit Launcher to use particular NUnit build for your tests.

To start the NUnit Launcher from any TeamCity build runner, use either the teamcity.dotnet.nunitlauncher NAnt property, or the environment variable of the same name, or the teamcity_dotnet_nunitlauncher MSBuild property. These properties should have the following mandatory parameters:

• .NET Framework version (both 1.1 and 2.0 versions are supported),
• The platform to run tests (x86, x64, and MSIL),
• The test framework version to use. TeamCity supports the following NUnit versions: 2.2.10, 2.4.1, 2.4.6, 2.4.7, 2.4.8, and 2.5.0 (Alpha 3)
• List of assemblies to test

In addition to the above-mentioned parameters, you can also specify filters by tests category and NUnit addins (for NUnit 2.4 and higher). Filters by tests category allow you to control a set of tests to run, if you use tests grouping by category in your project.

You can find the detailed description of TC NUnit Launcher syntax at TeamCity reference. Here, in this post, we will just illustrate it with the example below.
(more…)

In today’s episode of the NUnit mini-series we’d like to share some information on using TeamCity Addin for NUnit.

As we wrote in our previous post, to provide tests state tracking and on-the-fly reporting, TeamCity bundles NUnit and includes its own NUnit runners. These embedded runners suit most cases perfectly well but there can be situations when you:

• prefer to use particular NUnit instance (not TeamCity’s bundled) for your particular build configuration
• want to pass NUnit project file (.nunit)

For cases like these you can use a recently implemented TeamCity Addin for NUnit available in TeamCity 4.0 EAP; the Addin supports the following versions of NUnit: 2.4.6, 2.4.7, 2.4.8 and 2.5.0 Alpha3.

How does it work?
TeamCity Addin for NUnit is embedded in the system by default and contains .dll and .pdb files for each supported version of NUnit. For every build, the main part of a path to the TeamCity Addin is set to the build property and the environment variable of the same name:

• teamcity.dotnet.nunitaddin for NAnt
• teamcity_dotnet_nunitaddin for MSBuild

To enable on-the-fly tests reporting, all you have to do is to add a task in your build for copying an appropriate Addin’s files to your NUnit’s addins directory. Type your NUnit version at the end of the TeamCity Addin path using the following syntax:

• For NAnt: ${teamcity.dotnet.nunitaddin}-<NUnit version>.dll
• For MSBuild: $(teamcity_dotnet_nunitaddin)-<NUnit version>.dll

In the above filenames, the <NUnit version> parameter can possess the following values: 2.4.6, 2.4.7, 2.4.8, and 2.5.0.

Please note that we recommend to copy TeamCity Addin for NUnit files every time you run the particular build.

The following example for MSBuild shows how to use NUnit console runner with TeamCity Addin for NUnit 2.4.7:

<PropertyGroup>
   <NUnit>Path_to_NUnit_console</NUnit>
   <NUnitAddinsDir>Path_to_NUnit_Addins _Dir</NUnitAddinsDir>
</PropertyGroup>

<ItemGroup>
   <NUnitAddinFiles Include="$(teamcity_dotnet_nunitaddin)-2.4.7.*" />
</ItemGroup>

<Target Name="RunTests">
   <Copy SourceFiles="@(NUnitAddinFiles)" DestinationFolder="$(NUnitAddinsDir)" />
   <Exec Command="$(NUnit) $(NUnitFileName)" />
</Target>

Well, it’s again a time for a break. See you soon!

Technorati tags: TeamCity, JetBrains, IntelliJ IDEA, Eclipse, continuous integration, build management, agile development, NUnit, MS Visual Studio 2005, MS Visual Studio 2008

For those of you who use TeamCity version 3.1.1 or earlier, we present TeamCity 3.1.2 Release Candidate.

The upcoming release is mainly about bugfixes but also brings some enhancements to the current features, in particular:

• Improved Database Migration Tool is now more fail-proof.
• Version Control integration bugfixes are included, specifically for VSS, CVS and StarTeam.
• Visual Studio plugin now supports Subversion 1.5 working copy format.

In our issue tracker you will find the full list of fixed issues.

Download TeamCity 3.1.2 Release Candidate. As usual, we remind you to back up your data before upgrading to a new version.

Wish you happy building!
The JetBrains TeamCity team

Technorati tags: TeamCity, pre-tested commit, JetBrains, IntelliJ IDEA, continuous integration, build management, agile development, release candidate