JetBrains TeamCity Blog

Today we’re making available yet another TeamCity 7.0 EAP build with lots of cool stuff in it. As usual, you can get a taste of features that are going to be in version 7.0 even before it is released. So if you’re wondering, what is there – here’s a list of things you couldn’t do before, but can try out now:

View investigations assigned to you at one page

Previously, there was no specific place where you could see all investigations assigned to you. Of course you had notifications, and you could see this information in each particular build configuration, but it would be much more convenient to have a dedicated page for that – who knows how many projects and build configurations are affected by your changes and in how many of those you are supposed to investigate failures. Now it’s easy to take a glance at the whole picture – just click a little box with a number next to your name.

Drill down inside artifact archives

It is now super easy to browse inside artifact archives right from the TeamCity web interface!

Moreover, you can download some particular file from an archive using new URL syntax:
http://<server url>/repository/download/<build conf id>/<build>/<archive>\!<path in archive>
Plus it made easier configuring Report Tabs.

Disable build steps, triggers and more

Since we have introduced build steps, one of the most awaited features was an ability, to temporary or permanently disable some setting in build configuration. For example, if you have a configuration inherited from a template. Now you got it! Even better, you can not only enable/disable build steps, but also build triggers, build features and build failure conditions!

Use TeamCity as NuGet feed

TeamCity now can act as NuGet server serving NuGet packages published to TeamCity as regular build artifacts. When a build publishes NuGet package as artifact it is automatically added to TeamCity NuGet feed. This feature needs to be enabled explicitly on Administration -> Server Configuration -> NuGet tab.
Note, current implementation of NuGet shows all found packages within TeamCity installation. Access rights are only checked on downloading packages bits. There is a related issue for it though: TW-19157.

Work easier with agent pools, dependencies, R# inspections and so on

Of course, we also greatly improved features introduced in earlier EAP builds.

• For agent pools we’ve added ability to filter build queue by an agent pool; added grouping by agent pool on Agent Matrix and Agent Statistics pages; redesigned Compatibility pages; and more.
• .NET Inspections runner was improved in order to work correctly with LINQ usages, Silverlight projects, External annotations usages (NUnit) and Web Site, Asp.NET MVC projects.
• Dependencies graph introduced in previous EAP was greatly improved
• and much more – see the release notes.

Don’t forget to back up your TeamCity instance, try the build and help us make another one better for you!

Enjoy!

New bug-fix update is available – TeamCity 6.5.5. Several performance problems were addressed in this build, as well as quite old issue with symbolic links (TW-7938) and some other bugs: see the complete list of fixed issues.

Download the build and share your feedback with us.

Happy building!

New TeamCity 7.0 EAP build is ready and waiting for you to try! We have improved features introduced in the first EAP build, and of course we’ve got some completely new stuff.

.NET Inspections runner

Yes, it’s finally here and it’s based on powerful ReSharper code analysis engine! Now you can run .NET inspections and see the results right in TeamCity.

Global Maven settings

Previously you could specify path to alternative user settings file (equivalent to Maven command line option -s or –settings) in build configuration.  Now you can define these settings xml files globally in Server Configuration area, and use them in your Maven builds. When you create or modify a build configuration you will only need to select, whether you want to use default settings file (chosen by Maven), specified by path or global (uploaded on server). Since TeamCity stores these files under <TeamCity Data Directory>/config/_mavenSettings , you  can update them there whenever you need.

Per-check-in builds

If you have fast builds, you can now trigger them for each check-in, or for a group of check-ins made by the same user. Why? Thus you will see right away who broke what! When a build contains one check-in, or a couple of check-ins by one user, there can be no doubts, who’s responsible for a new failed test.  ;)

Fail build on a specific text in build log

We’ve already mentioned this feature in one of the recent posts, though we have improved it since then and we would like to hear your feedback on it.

Graph of commits

If your project uses Git or Mercurial you can see graph of commits on build configuration change log page. Graphs are also useful for non-DAG-based VCSs: they make it easier to understand where a VCS root modification comes from.

…and the rest gets only better!

We’ve improved, reworked and made better:

• Administration interface for Agent Pools
• Snapshot dependencies graph
• Tree view in build log
• NuGet integration
• and more…

Don’t forget to back up your TeamCity instance, try the build and help us make another one better for you!

Happy building!

Look out world, we have just opened early access program for the next TeamCity version: code name Faradi. That means you can download the first TeamCity 7.0 build right away and try all the cool features that are in it. Want to know what features are there? Here’s a list:

Build Failure Conditions – Smart Control Over Your Build Status

TeamCity has become smarter in deciding when a build is to be considered “failed” – now it can look beyond the obvious like exit code or failed tests presence. Basically, you can instruct TeamCity to mark a build as failed if it has become “worse”. There is a number of metrics in TeamCity already to measure how “good” a build is, like code coverage, or artifacts size, etc., so all you need now is set up the threshold for those metrics that are important to you. For instance, you can mark build as failed if code coverage or code duplicates number is worse than in the previous build. Learn more about this feature from the related post. However, that’s not the end of the story. Another build failure condition is on its way – it’ll allow to mark build as fail when a certain message is met in build log. This functionality is still quite raw though.

By the way, don’t panic when you don’t find good old “Fail build if” conditions that used to be at the General Settings page – we didn’t drop them, just moved to the new page with the rest.

Agent Pools – Better Agents Management

Starting with TeamCity 7.0 it’s easier to organize your build agents and calculate the required agents capacity. Instead of having a a single set of agents, you can now break it into smaller groups called agent pools. In two words, a pool is a subset of agents to which you can assign projects. Thus you can run your project on a subset of agents and make sure no other projects will run in the same pool.

Dependency Based Test Run – Faster Builds

Maven, Gradle and IntelliJ IDEA Project build runners now support dependency based run of tests. One of the best practices in software design is to make modules as independent as possible, and if you follow this practice, now you can get an extra bonus – faster builds in TeamCity, because TeamCity can run only those tests that are really affected by changes in dependencies.

Learn more in the release notes.

NuGet Support

TeamCity now comes with native NuGet support. The plugin that provides NuGet support has become available a couple of weeks ago, and now it is bundled with TeamCity. There was a series of blog posts dedicated to this plugin, so we won’t go into details here:

• http://blogs.jetbrains.com/dotnet/2011/08/native-nuget-support-in-teamcity/
• http://blogs.jetbrains.com/teamcity/2011/07/20/nuget-plugin/
• http://blog.jonnyzzz.name/2011/07/nuget-publish-build-runner.html

As a side note, the plugin is compatible with TeamCity 6.5, so if you want to use it in your existing production server, you can download it at teamcity.jetbrains.com.

And a bunch of other features…

… including build performance monitor, improved My Changes page and Build Log, support for Subversion 1.7 in Visual Studio Addin, and so on. See the complete release notes, try the build and share your feedback with us!

Don’t forget to back up your TeamCity instance, and note that starting with this version TeamCity server and agent require Java 6.0 or later.

Stay tuned, we’ve just got the ball rolling!

While the work on TeamCity 7.0 is already in progress, we keep polishing the 6.5.x branch. Here’s new bug-fix update – TeamCity 6.5.3, that addresses issues related to MS SQL problems in the first place and includes some other fixes.

See the complete list of changes, download the build and share your feedback with us.

Don’t forget to back up your data before upgrading.

Bug-fix update for TeamCity is available and we strongly recommend all TeamCity 6.5 user to upgrade. This update addresses problem with slow clean-up on Oracle DB, and some other critical issues.

If you failed to upgrade with version 6.5, make sure you give 6.5.1 a try: it contains a number of fixes related to upgrade process.

See the complete list of changes, download the build and share your feedback with us.

TeamCity takes yet another step towards complete perfection by releasing version 6.5 – it’s here, it’s available, it’s waiting for you to download and try it. So what’s in the box?

• Remote run on changes in DVCSs branches: New build trigger added that watches for commits into Git or Mercurial branches and adds personal build to the build queue when commit detected.
• Parameterized Version Control System roots: Parameter references can now be used in all text fields of a VCS root settings except, of course, password fields.
• Tests grouping: To help you identify common problems faster tests can now be grouped by package on the build results page, Current Problems page, My Changes and in many other places.
  
• Muting test failure: If some tests fail for a known reason and it is not possible to fix them right away, you can temporarily mute them. For example, if your test is failing intentionally, when required functionality is not yet written (TDD).
• Remote build agent installation: New experimental way to automatically install build agents on the machines in your network or in the cloud called “Agent Push”.
• JetBrains dotCover 1.1 integration: TeamCity VS-addin can download dotCover test coverage snapshots from the TeamCity server and open them right in the dotCover installed in your Visual Studio locally.
• .NET: A number of new feature is available for .NET deveopers, such as:
  • AssemplyInfo Patcher build feature that allows to set a build number to an assembly automatically, without having to patch AssemblyInfo.cs files manually.
  • PowerShell: dedicated build runner for PowerShell scripts.
  • MSpec: built-in MSpec runner designed specifically to run MSpec tests.
  • .NET process runner able to run any .NET assembly under selected .NET Framework version and platform, optionally with .NET code coverage.
• and much more.

But that’s not the end of the story. We have some trully great news for small and medium-size teams that use TeamCity Professional Edition (which is free, as you know). Starting with this release we have removed all restrictions except one: the maximum number of build configurations. This gives TeamCity Professional Edition users following advantages:

• Unlimited number of users.
• Ability to use any authentication scheme.
• Adjustable per-project permissions.

Happy building!

There are just a few days left before we release TeamCity 6.5, but to ease a little bit the tension of waiting today we publish the release candidate build. Comparing to the previous EAP build it doesn’t bring any new features, but contains a number of bug-fixes, so if you’re eager to try TeamCity 6.5 asap – this build is for you.

Take a look at the list of resolved issues, download the build and don’t forget to share your feedback with us!

Meet fresh bug-fix update for TeamCity – TeamCity 6.0.3. Here are some noteworthy fixes:

• TW-15296: “Cleanup after some archived-build deletions takes 6.5hr”.
• TW-15335: “Xml report plugin eats too much CPU”.

Plus, now TeamCity recognizes and displays on the Tests tab FlexUnit tests ran by flexmojos-maven-plugin.

See the complete list of changes, download the new version and share your feedback with us.

Don’t forget to backup your data before upgrading.

Guys from the YouTrack team have great news that we’ve considered worth spreading further, and I believe you are going to be as much excited as we are here.  Now, if you’d like to use YouTrack, you don’t need to install or setup anything, because YouTrack Hosted Beta is now available! Join the beta testing group today and get:

• 50 user accounts
• Unlimited number of projects
• FREE use until July 1, 2011

And enjoy all the benefits of hosted issue tracking with YouTrack:

• Full YouTrack functionality + all new features
• Daily backups
• Import from other bug trackers using YouTrack  Python Client Library
• Automatic migration to hosted production
• No-effort migration to standalone YouTrack using the hosted db backup
• RESTful API for integration with third party tools

Get YouTrack Hosted Now!

Note, the number of the hosted beta instances is limited!

Interested in YouTrack? Find more about it’s features and updates in its blog.