JetBrains TeamCity Blog

TeamCity’s Build Agents run the software builds and altogether make the company’s Build Grid. To be able to run some build, the Build Agents must meet the requirements of the build configuration. If there is a free build agent matching the build configuration requirements is found when triggering the build, the build is started. Otherwise the build enters the Queue and is processed when a compatible build agent becomes free.

In TeamCity 3.0 you can establish a run policy for different build configurations selecting to run:

• only specific build configurations
• all build configurations compatible with the build agent

Such approach as we believe will allow to manage the build agents’ workload more effectively. Lets look at a quite common situation: if performance tests (as a rule taking much time) are run, the build agents which have low hardware resources may slow down, more builds will enter the build queue, and the feedback is not so quick as you would like it to be. To avoid such situation, define the run policy for the build configurations which can be run on the build agent. Do it when setting up the project or build configuration and any moment you need:

1. Click the Agents tab.
2. Navigate to the desired build agent.
3. Click the Compatible Configurations tab.
4. Select Run selected configurations only and tick the desired build configurations names to run on the build agent.

The changes are applied on the fly as usual.

And vice versa: you can make the build agent name or property a must-have requirement for the build configuration. As a result, TeamCity will create builds of the build configuration only on specific build agents.

More details on this are available in TeamCity online reference.

Technorati tags: TeamCity,build agent, build queue, JetBrains, IntelliJ IDEA, continuous integration, build management,agile development

The most essential steps for the software developers of their daily chores are modifying the code, integrating the changes, and waiting for feedback on changes integration. Depending on the project scale it may take a significant amount time. And if the developer’s changes break the code base, fixing the problem and verifying the changes always takes time. Meanwhile the development process can simply freeze, time is wasted, and deadlines are missed.

We decided to change the situation for the better: compared with the standard scenario – edit the code, commit, and verify the code quality – TeamCity’s pre-tested commit allows you to remotely verify your changes before committing them to the version control system. Thus, the project code base is always clean.

You may have noticed a new page has recently appeared on TeamCity’s web site providing the visual description of pre-tested commit.

In the nearest future we plan to publish a big article with pre-tested commit description: feature history, workflow, peculiarities in different IDE’s, and more.

Good news for the .NET platform developers: in TeamCity 3.0 you can perform pre-tested commit from within Microsoft Visual Studio 2008 Beta 2. The EAP build is already available for download.

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

Even though it’s a holiday season now, we keep on working here, at JetBrains, to bring you more features you want to be implemented and asked for. So, after several weeks of hard work a new TeamCity 3.0 EAP build is available!

This EAP features highlights:

• .NET projects code quality improvements: search for code duplicates for C#
• the so-long awaited statistics: view the builds’ duration, artifacts’ size, and code coverage trends



• downloadable build log (available in text format)
• enhanced customization possibilities for build results: build status and its description, and the build number can now be modified by the build process
• MSBuild build runner improvements: support of MSBuild build started from within the NAnt script (by NAntContrib msbuild task. For more details, please access TeamCity documentation)
• in addition to supported NUnit2 task for NAnt, we have improved the already existing support for NUnit task of MSBuild (from the MSBuild Community Tasks project). No need to modify existing scripts to run them under TeamCity: get the improved output automatically.
• build tests view allowing you to view how long each test ran, their status and other info and sort them out simply clicking the desired column



• remote run and pre-tested commit for MS Visual Studio 2008 Beta 2

View the release notes and download the latest build.
We wait for your feedback in our discussion forum.

Technorati tags: TeamCity,JetBrains,IntelliJ IDEA, continuous integration, build management,agile development,MS Visual Studio 2003

We are glad to share good news on TeamCity’s success with you. Many readers of Java Developer’s Journal which is the world’s leading Java resource gave their votes for TeamCity. It has become a winner in the best team development tool category together with our flagship product IntelliJ IDEA 6.o. Besides, TeamCity is a finalist in the best Java project build tool category.

We really appreciate your support and want to thank all those who took their time to vote for TeamCity. We keep on working on improving the existing features and adding new ones, and hope our products will meet your expectations in the future.

Participate in TeamCity early access program to stay tuned with the current project’s status and download the latest TeamCity EAP build.

Technorati tags: TeamCity, JetBrains, JDJ Awards, IntelliJ IDEA, continuous integration, build management, agile development, Subversion, TFS, CruiseControl, ClearCase

We keep on getting feedback on TeamCity’s advantages in continuous integration and agile development practice from our users. Michael Hüttermann, a well-known author of a book on agile software development, Sun Java Champion, member of Agile Alliance, a coach and consultant for JEE and agile development has recently published a second article on TeamCity in Javamagazin (issue 9, 2007). In the article he shares his positive user experience with TeamCity and provides:

• a summary of TeamCity’s concepts and possibilities of its user interface
• some notes on initial TeamCity installation and startup
• a howto on configuring the project settings via TeamCity’s web interface and migration from CruiseControl to TeamCity
• a description of IntelliJ IDEA 6.0 integration plugin for TeamCity

The article is currently available only in German at Michael Hüttermann’s website, and we hope it will soon be translated into English.

Technorati tags: TeamCity, JetBrains, IntelliJ IDEA, Java, continuous integration, build management, agile development, Subversion, TFS, CruiseControl, ClearCase

Hello,

We are glad to announce the first EAP build of TeamCity 3.0 (codename Benares). It has significant number of new features as well as fixes, usability and performance improvements. It is pretty stable – we run TeamCity EAP as an internal JetBrains build server which serves dozens of projects of various types (.NET, Java) in multiplatform environment (MacOS, Windows, Linux).

Most noticeable features of this build include:

• Per build configuration, shareable VCS Roots
• Visual Studio pre-tested commit support for Subversion
• StarTeam support
• Build queue now features estimated build start and finish times
• Possibility to assign agent to specific build configurations
• Detection of hanged builds
• Multiple UI improvements

and other issues.

We have much more plans, with primary focus on statistics and per-project access rights. Stay tuned with Benares early access program.

Download TeamCity Benares EAP build

Kind regards,

—JetBrains TeamCity team

TeamCity, JetBrains, continuous integration, build management