JetBrains TeamCity Blog

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…)

When running your builds, TeamCity selects between the build agents taking into account a whole set of different factors and parameters. First and foremost, it tries to run the build on the fastest available build agent based on builds history of a build configuration on this agent. And since the available build runners depend on environment where the agent is running, TeamCity chooses an agent having required a build runner.

Until recently it was possible to run the build on desired build agent only from the web interface by, for example, clicking the Run button and selecting the desired agent from the list. The Run configuration policy, which we have told you some time ago, allows to make TeamCity create builds of some build configurations only on specific build agents. As a result, TeamCity will create builds of the build configuration only on specific build agents no matter if they are initiated:

• manually (either from the web interface or using the pre-tested commit)
• automatically when the changes appear in the version control system
• periodically (a time-based trigger is enabled)

With TeamCity plugin for IntelliJ IDEA you can now opt to select one or several build agents to run your personal build on. Such approach allows you to test your changes with more granularly under:

• desired platforms,
• operating systems,
• databases,
• environment variables.

which are specified for the build agent available in your company’s build grid:

The latest builds with the updated IntelliJ IDEA plugin are available at our EAP page.

We hope you will greatly enjoy the feature and use it on a daily basis.

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

The release of TeamCity 4.0 is not far away, and you have a chance to try a number of its cool new features right now:

• “same sources” dependencies between the build configurations ensuring your build starts only after the build it depends on is run and finished
• “history builds” getting the desired changes from the list of the latest ones
• enhanced search allowing to find builds by their status text, VCS label, test name, trigger name, changes committer and more
• multiple user interface changes including redesigned Change Log and others

Download the latest EAP build, read new features description in the release notes and familiarize with the list of fixed issues.

And, as usual, we urge you to backup your data before upgrade to a new version.

Wish you a happy building and eagerly wait for your feedback!
The JetBrains TeamCity Team

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