JetBrains TeamCity Blog

Yet another update for TeamCity is now available – TeamCity 5.1.3. In this version:

• Added support for Cucumber 0.8.5 and RSpec 2.0 beta.
• Rake runner can now use interpreters installed by means of RVM.
• Fixed several critical bugs to make TeamCity more stable and reliable.
• Plus some important issues were fixed in TeamCity Visual Studio add-in.

We recommend you to take a look at the complete list of changes and upgrade to the new version. Feedback is always welcome!

As usual, we remind you to backup your data before upgrading just to be on the safe side.

The JetBrains TeamCity Team

In the first TeamCity 6.0 EAP you can find the long-awaited feature — build priorities; you asked — we did it. Moreover, since it is implemented as a Build Queue Priorities plugin for TeamCity, it is also available for TeamCity 5.1.x.

Now you can control build priorities by creating so-called Priority Classes — in two words, a priority class is a set of build configurations with a specified priority. Naturally, these classes can be configured from the Build Queue page, but note that only users with System administrator role can access these settings.

You can add as many priority classes as you need, add build configurations to them according to your needs and define the priority in the range -100..100. This setting is taken into account only when a build is added to the queue. The builds with higher priority will have more chances to appear at the top of the queue; however, you shouldn’t worry that the build with lower priority won’t ever run. If a build spent long enough in the queue, it won’t be outrun even by builds with higher priority.

Also note that by default you already have two predefined priority classes — Personal (priority=10) and Default(priority=0).
The first one is used for personal builds (Remote run or Pre-tested commit) only, i.e. any personal build added to the queue will be assigned to this priority class. The Default class simply includes all the builds not associated with any other class. This allows to create a class with priority lower than default and place some builds to the bottom of the queue.

We’ve had a lot of discussions about this feature, because there were many ways to implement it. We picked the one that seems the best, however we encourage you to try it and share your feedback with us. Try it!

The JetBrains TeamCity Team

Hello all,

This is a post for those of you who’s currently trying (and failing) to buy something from JetBrains, or to submit a bug into our issue tracker, or contribute to one of our community resources.

Today the extreme heat in Europe finally took a toll on us in the form of blackout that temporarily took down a part of our online assets.

While the majority of resources at jetbrains.com is available, our e-shop section is down (which is why you aren’t currently able to order any of our products), as are our bug tracker, wiki, and forums.

We’re regularly getting updates on the recovery progress, and the current (quite rough) recovery time estimate is today evening, 19:00 CET.

We apologize for the inconvenience, and we’re really hoping for a quick recovery.

Update! Seems like it’s all over, and on schedule! Power supply is resumed, meaning that YouTrack, Confluence, and JetBrains e-shops are now back online, and our support service is working well!

Last week two our team members, Sergey Anchipolevsky and Max Feldman, went to Israel and have participated in the Continuous Integration & Build seminar “To Build or Not to Be” held by JFrog. By the way, JFrog has recently announced the release of a great plugin for TeamCity — the result of joined efforts of JFrog and JetBrains teams.

The seminar gathered a lot of great people. It was interesting to meet with Kohsuke Kawaguchi — creator of Hudson, and Hans Dockter — the founder of Gradle. The guys were truly excited by Hans Dockter’s talk about his brainchild — Gradle, an enterprise-grade build system. Hans Dockter greatly appreciated TeamCity and suggested the collaboration to provide an integration of TeamCity and Gradle.

Everyone agreed about the common goals to promote Continuous Integration practices and we’ll definitely combine our efforts on the forthcoming JavaOne 2010.

We would like to thank Shlomi Ben-Haim, CEO of JFrog, for the invitation, the cordial welcome, for organizing the meetings for us, and we look forward to further cooperations.

Check out some pictures from the event.

If you have any thoughts, we definitely want to hear them!

We would like to announce that today we’re opening Early Access Program for TeamCity 6.0.
Here’s a short summary for this EAP:

• TeamCity now treats more carefully builds that cannot start due to some configuration errors, for example when VCS repository is down on build start, or artifact dependencies can’t be resolved, etc.
• Agent-side checkout is now available for Perforce and ClearCase.
• Implemented new IntelliJ IDEA project runner.
• Swabra plugin is now bundled with TeamCity.
• We’ve added the long-awaited feature – build priority classes, which allow you to flexibly adjust the order of the builds in the build queue.
• Visual Studio Add-In was improved.
• Added VCS trigger rules for commit message.
• and more.

View the build’s release notes and complete change log, and try it.

Looking forward for your feedback!
Sincerely,
The JetBrains TeamCity Team