JetBrains TeamCity Blog

Today we have become one step closer to TeamCity 6.0 release, and I believe this release candidate may be the last EAP before reaching the finishing line and publishing the major build. Our team is now focused on polishing TeamCity up, and we put all our efforts to refine the features you could already try in previous EAP builds. That’s why this build mostly contains bug-fixes and basic improvements. Take a look at the list of changes included, download the build, and, of course, tell us what you think about it. As usual we remind you to back up your data before upgrading.

Hold you breath, the final countdown is on!

As the major TeamCity 6.0 release approaches, the release candidate build is already available. Besides bug-fixes, it contains several enhancements and improvements. For example:

• dotCover coverage engine now reports statement coverage instead of line coverage.
• .NET coverage options are now available in MSTest build runner.
• For each Maven build TeamCity agent gathers Maven specific build details, which are available on the dedicated “Maven Build Info” tab after the build is finished.



• Swabra settings now reside in a separate section called “Build Features” which is available on “Build Steps” page.
• and more.

As usual, we remind you to back up your data before upgrading to a new version. Stay tuned, the big day’s closer than it might seem;)
Download TeamCity 6.0 RC.

New TeamCity 6.0 EAP build is now available with Gradle support described in previous post and several new features and major improvements:

• Improved upgrade procedure. First of all, we have reworked the upgrade procedure. Though it already was quite painless, we’ve made it more explicit and smooth. Usually, a typical TeamCity upgrade requires conversion of database and configuration files. Since, previously this was performed automatically, it could be not clear what and why had happened. Now, when TeamCity decides that the data conversion is required, it asks for confirmation from server administrator and suggests to perform a backup (which we highly recommend in any case). Thus you’ll always know what’s going on, and when it’s time to back up your TeamCity instance. Automatic backup will be available, but only starting with version 6.0 or higher.
• Ability to explicitly select build configurations for an agent. Though TeamCity can distribute builds to agents based an agent requirements specified in build configurations, we know that some of our users prefer to explicitly specify which configurations can be built on which agents, and do not want to allow building of other configurations on these agents. That was possible in previous TeamCity versions, but starting with this EAP we have improved the UI for manual configurations selection. Give it a try! We believe, new UI has become better and more convenient, even if you have a huge number of build configurations.
• Auto-Completion in agent requirements. Now specifying agent requirements is easier and faster – just start typing a parameter’s name or value. Plus, you can see how many agents have this parameters defined, and with what values.
  
• JetBrains dotCover integration. Recently our .NET guys have released a brand new .NET coverage tool called dotCover, which includes lots of neat features, like reporting statement-level coverage in .NET Framework and Silverlight applications, highlighting for covered and uncovered code right in Visual Studio, detecting which tests cover a particular location in code and much much more. Starting with this EAP, this promising coverage engine is bundled with TeamCity and is available next to NCover and PartCover.
  
• and more…

See the release notes for complete list of changes, download the build and send us your feedback!

And as usual, don’t forget to back up your data!;)

Java build tools are evolving constantly. Good old tools become better, while new tools appear frequently. One of the new ones, called Gradle, aims to bring together powers of Ant, Maven, Ivy, and spice them up with Groovy language. From the Gradle page you can learn more about its benefits.

If you feel interested in it, you’ll probably like that in TeamCity 6.0 we are going to add full-fledged Gradle support. A tiny piece of Graddle runner has already appeared in the previous TeamCity EAP. Since then we’ve done a lot of improvements:

• Better failing tests reporting.
• Correct reporting of tests executed in parallel tasks.
• Code coverage: activate built-in IntelliJ IDEA code coverage, and get overall and detailed coverage statistic.
• Build Properties configuration. Use build and agent properties inside your Gradle build.

If you already have a Gradle build, you are likely to be using Gradle-wrapper. Gradle Wrapper support is on its way as well, allowing you to create Gradle build configuration for TeamCity in no time. Just point TeamCity to your version control, mark appropriate checkbox – and you are ready to go! You won’t need to install and configure Gradle runtime distribution to any of your build agents.

Migration to Gradle is rather simple, or almost invisible, e.g. for maven2 builds. Try Gradle runner in the forthcoming EAP and tell us what you think!