Released: Dec 13, 2010

Updates in this release

Updates in V6.0

• Build steps
  When creating a build configuration, you can now configure the sequence of build steps to be executed. Each build step is represented by a build runner and provides integration with a specific build or test tool. You can add as many build steps to your build configuration as needed.
• New "My Changes" page
  For TeamCity 6 release JetBrains has carefully re-thought a concept of the My Changes page, and made some radical changes towards usability and navigability. The new "My Changes" gives you a nice overview of how well your commit integrates in different builds and build configurations. It also supports keyboard navigation, which allows you to locate problems faster and in more comfortable way.
• New IntelliJ IDEA projects build engine
  TeamCity 6 uses a rewritten build engine for IntelliJ IDEA projects, similar to the one found in IDEA itself. You can now run IntelliJ IDEA shared "run configurations" in TeamCity, and also produce all kinds of IntelliJ IDEA artifacts, including wars, ears, GWT artifacts, etc. Last but not least, IDEA projects in TeamCity can now be configured to only compile modules, required to run tests or produce build artifact, instead of recompiling and testing the whole project.
• Support for Gradle and Maven 3
  Gradle is a build automation tool with lots of features. JetBrains has created a full-fledged Gradle build runner, which supports all of the advanced TeamCity features. TeamCity 6 now includes dedicated Maven support and is now fully compatible with Maven 3.
• Bundled plugin for an automatic build directory clean-up
  Builds often produce a lot of garbage which should be cleaned before next build starts in the same directory. "Swabra" plugin remembers the state of the build checkout directory, and when next build starts in this directory, Swabra finds all of the files added by the previous build and removes them.

For more information visit:
http://www.jetbrains.com/company/press/pr_011210.html