TeamCity 7.0: Control The Power

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.

•

•

Extended build chains support and visualization

Build chains give you a unique ability to define a sequence of builds and run them consistently, on the same source files revisions.

The main purpose of build chains is to let you define your own delivery pipelines with TeamCity in the most flexible way.

TeamCity 7.0 takes build chains support even further, providing an insightful overview of the completed and running build chains, with all the effective builds and their statuses.

If you chose not to trigger some of the builds automatically, such builds work as manual pipeline stages. Once you trigger them manually, the build sequence continues its execution.

•

•

Build parameters with custom UI

The ability to run custom builds has always been one of TeamCity's distinctive features. In TeamCity 7.0, it gets even better.

You can now specify a certain type for any custom parameter you define in either build configuration or the project. Based on this type, the Run Custom Build dialog will present a specific UI control for this parameter, be it a text field, checkbox, select, or password input.

If it's a password, it'll be kept secret and will never appear in any TeamCity files, such as logs, in unscrambled form.

•

•

Performance monitor

When your project expands and the number of unit tests grows to several thousands, your builds can become really slow. It isn't always obvious how to make them faster or even where to start.

With TeamCity 7.0, you can trigger performance monitor, and have detailed information on hardware resources utilization at each step of your build process.

This unique feature can help you nail down many build performance problems, from reaching memory and disk throughput limits, to suboptimal multi-core CPU utilization.

•

•

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.

TeamCity 6.0

December, 2010

• Build Steps
• New "My Changes" page
• New IntelliJ IDEA projects build engine
• Support for Gradle and Maven 3
• Lots of other improvements and fixes

TeamCity 5.1

April, 2010

• Improved support for .NET 4.0 and Maven
• Many features towards general usability
• Better server administration and configurability
• Enhanced IDE Integrations
• Stability improvements and bugfixes