JetBrains TeamCity Blog

Among many other plans for the forthcoming TeamCity 4.0 release, we want to extend the list of supported version control systems, and this time we bring you the long-waited Mercurial.

At the moment Mercurial support is implemented via a plugin enabling:

• server-mode checkout
• collection of developer’s changes
• checkout rules support and checkout on the server

In our nearest plans are remote run, checkout on the build agent, and bundling the plugin into TeamCity installation package.

The plugin it is compatible with TeamCity 3.1.x and TeamCity 4.0 EAP builds. Meanwhile, you can download plugin files at our public demo server. Look for TeamCity Plugins project, Mercurial SCM Support build configuration and download either mercurial-server.zip or mercurial-src.zip file.

Follow these simple instructions to enable Mercurial support in your TeamCity installation after downloading the mercurial-server.zip:

• for TeamCity 3.1.x server, move the mercurial-server.zip to the WEB-INF/lib directory of the TeamCity server,
• for TeamCity 4.0 EAP builds, put the whole zip archive into the .BuildServer/plugins folder and restart the server.

The mercurial-src.zip contains the plugin sources available under the terms of Apache 2.0 license, and you can also obtain source code of the plugin from the mercurial repository where it actually resides.

We wait for your feedback and suggestions and wish you a happy building!

Technorati tags: TeamCity, JetBrains, Java, VCS, .NET, IntelliJ IDEA, continuous integration, build management, agile development, best practices, MS Visual Studio 2003, Eclipse, Mercurial, CMS

Hi folks,

A few of us are going to the Agile2008 conference in Toronto next week, and we’d love to meet up with you. Are you planning to go?

We’d love to hear your stories and feedback — and check out the event together. Ping david.booth(at)jetbrains.com and we’ll figure out the best way to meet while we’re all in the same place!

(We’re not exhibiting at the event, but we WILL have some TShirts to give away to a few lucky fans if you catch us quick enough

See you soon!

David Booth & Max Feldman

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

With this overview post we start a blogging mini-series about .NET and NUnit support in TeamCity.

For .NET platform builds TeamCity supports several build runners, in particular:

• NAnt
• MSBuild
• sln2003, sln2005, and sln2008

bundles NUnit testing framework (versions 2.2.10, 2.4.1, 2.4.6, 2.4.7, 2.4.8, 2.5.0 and later), and provides NUnit runner for your tests.

No matter which NUnit version you choose, TeamCity can track the tests and report all the information on-the-fly (both in the web UI and your IDE). You do not have to wait for your build to finish to discover that something went wrong. TeamCity informs you about tests failure immediately and provides details on occurred errors, so you save your time. By the way, in TeamCity web UI for each failed or ignored test you’ll find a direct link to open it in your IDE. With tests tracking feature you get on-the-fly all important information about every test you’ve run within a build: its status, name, package, duration, and statistics.

Besides, we eased a headache with running your tests under x86 process on the x64 machine by introducing an explicit specification of the platform and runtime environment versions. You can define whether you use .NET 1.1 and MSIL, x64 or x86 platform to use for .NET 2.0 version.

We also have good news for those who use NUnit addins. In TeamCity 4.0 EAP we have implemented support of NUnit addins for TeamCity NUnit Runner. Please note that this feature is supported for NUnit 2.4.6 and 2.4.7.

To run tests with NUnit, TeamCity:

• uses its own NUnit launcher
• automatically replaces NUnit calls from NAnt with <nunit2> task
• automatically replaces NUnit calls from MSBuild with <NUnit> task from the MSBuild Community tasks
• provides TeamCity addin for NUnit to enable on-the-fly tests reporting from the existing NUnit (2.4.6 or 2.4.7 versions) instead of using bundled TeamCity NUnit runner.

And last but not least feature we’d like to mention here is the Risk group tests reordering. Recently we’ve published a tip on this feature for the Ant and Ipr build runners, and voila! — since the latest EAP you can instruct TeamCity to run recently failed tests before any others. Using this feature, please remember that tests are reordered within every NUnit tests run instance in your build.

Well, lets have a break for now and dive into details in our future posts.

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

After, yes, we admit, a long break we unleash a new EAP build of TeamCity 4.0 which has a great number of new features, plus multiple performance improvements and bugfixes. Among the major ones:

• reordering of NUnit tests
• redesigned plugins packaging
• possibility to redefine certain build parameters on manual build run
• running personal builds on a specific build agent from within IntelliJ IDEA
• configurable charts on Projects page
• support for Diana (IntelliJ IDEA 8 EAP project file format)
• and much more…

Please download this build and familiarize with the release and upgrade notes.

Happy building and wait for your feedback!

Technorati tags: TeamCity, JetBrains, IntelliJ IDEA, Eclipse, EAP, roadmap, continuous integration, build management, database, MySQL, PostgreSQL, oracle, MS SQL 2005, agile development, MS Visual Studio 2005, MS Visual Studio 2008