If you are a true fan of DVCS and branches workflows like Git-flow, you'll definitely appreciate the fresh branches support added in TeamCity 7.1. Our goal was to make development and building in branches as simple as possible, with minimum configuration required. And that's exactly what we've done.

Just push your branch to Git or Mercurial repository — and TeamCity will detect it and start a build on your changes.

Read more on feature branches in TeamCity »

Xcode runner

TeamCity edges one step closer to being the ultimate build system by adding a native Xcode runner.

Support for both Xcode 3 and Xcode 4 projects includes: automatic detection of Xcode presence on agent; on-the-fly reporting of tests started by Xcode build; and build log parsing with detection of compilation errors.

Visual Studio

TeamCity VS-addin is now fully compatible with Visual Studio 2012 including the dark theme support.

Change log and changes pages

Updated Build Changes and Pending Changes views now have a unified look with the main Changes view, as well as the ability to filter changes by user or file path.

"Show builds" and "Show graph" options, once enabled, add build markers on the graph so you can see exactly which commits are included in which build.

Build Agent Pools

Remember the days when you had to wait for a free build agent to have your changes built and tested? Forget them. Now you can organize build agents in pools and assign them to build your project only.

You can easily distribute agent pools among divisions or project teams, and also assign them based on the priority of your building tasks.

Why not have one or two spare build agents as a Priority Lane for your VIP projects?

Incremental builds

Use the advantages of your projects' proper module decomposition to significantly reduce the build and unit testing time.

Incremental builds is a new option in TeamCity that allows you to re-build and re-run only those modules and tests that are affected by the changes in the build.

At this time, this option only works for Maven, Gradle and IntelliJ IDEA projects.

Build failure conditions

Previously, you had an option to mark a build failed if at least one test failed. We thought that was not flexible enough, so we added more powerful failure conditions.

You can now choose to mark builds as failed on metrics change, and on specific text pattern occurrence in the build log.

Branch graphs on change log

The usability of modern distributed version control systems often becomes a matter of good tooling.

TeamCity 7.0 makes working with Git and Mercurial a pleasure, thanks to interactive branch graphs on the change log page. These graphs provide clean and accurate reading of all branches and commits.

ReSharper inspections

Great news for all .NET users and all ReSharper enthusiasts: starting with TeamCity 7.0, ReSharper Code Analysis is available on the server side as yet another inspections runner.

ReSharper Code Analysis helps you detect problems in C#, XAML, XML, and ASP.NET code.

NuGet: TeamCity as NuGet feed server and more

NuGet is a new tool for dependency management in .NET projects, which is quickly gaining well-deserved popularity.

TeamCity 7.0 comes with an extensive NuGet integration, supporting following scenarios: installing and updating NuGet packages on agents, creating, and publishing package to a given NuGet feed.

TeamCity 7.0 can also act as NuGet feed server, and trigger builds on changes in a specified NuGet package.

My Investigations notification

After you spend some time working with investigations in TeamCity 7.0, you'll start noticing a small counter near your name in the top right-hand corner.

Each time a new problem is assigned to you for investigation, the counter becomes orange, showing you the actual number of problems assigned. Click on the counter to instantly navigate to the My Investigations page.

It is an extremely handy tool, and a nice addition to TeamCity.