JetBrains TeamCity Blog

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!

We are glad to announce one more EAP build before final 6.5 release which should happen really soon, probably on the next week. And with this EAP we’re bringing some really good news for the users of TeamCity Professional. We decided to remove almost all of the Professional mode restrictions, except one: the maximum number of build configurations. Feel free to use any authentication scheme, any number of users and per-project permissions in your Professional installation!

We also improved remote run on branch feature, added some new plugins and fixed a lot of bugs. See full list of changes in change log. Download new build, and tell us ASAP if anything is broken.

Happy building!

There is not too much time left till TeamCity 6.5 release. We plan to release it in May, hopefully in the first part of the month. Since previous EAP build, we’ve made significant progress and as a result we are ready to announce another TeamCity 6.5 EAP build with some noteworthy changes.

First of all, those who use TeamCity and dotCover absolutely must try our new feature: VS addin is now able to download dotCover coverage snapshot from the TeamCity server and show it in the Visual Studio. Note that for this you’ll need nightly build of dotCover installed in Visual Studio.

Another interesting feature (and one of the most voted in our tracker) is the ability to use parameter references in VCS root settings. For example, in VCS root you can specify %branch% instead of real branch name. Actual value of the branch parameter can be set in parameters of build configuration or project where this VCS root is used. Thus you can effectively have much more generic VCS root settings and share them among many build configurations and projects.

You should also take a look at the finished build parameters feature. Have you ever asked a question with what exact parameters (environment variables or properties) your build ran on an agent? Now you have the convenient way to see all of them.

See full list of changes is listed in our change log. Download this build and share your feedback with us. Note that on the first start with existing data this build will need to perform data conversion so do not forget to make a backup. Fortunately now you can do it right from the TeamCity startup screen.

Happy building!

It’s been a while since our last TeamCity 6.0 EAP, and now we are ready to open EAP for TeamCity 6.5. Yes, we decided to call it 6.5, and the planned release date is the end of April – beginning of May.

In this EAP you’ll find the restyled web interface. We started to work on it before TeamCity 6.0 version is released, but decided not to include it in 6.0 version. Now we roll it out. We hope that you’ll share your feedback with us.

Another interesting feature is for those who use distributed version control systems. Now, TeamCity is able to monitor branches in Git or Mercurial repositories (such branches should have some specific names) and start personal builds once the push in the branch is detected. This feature is a bit experimental, we still not sure how it’ll look finally, and it has some bugs (TW-15302, TW-15137), sorry for that. But still we think it’s worth to show it to our users.

Of course, there are other features, like showing of the build configuration changes in the audit log, project parameters and more. See the complete list in our changelog, download the build and send us your feedback!

And don’t forget to back up your data before upgrade!

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!;)

As we promised, we continue the configuration parameters story started in the previous post. Today, I’d like to tell you about .NET related properties.
TeamCity .NET plugins provide a bunch of predefined properties indicating that .NET Framework/SDK/Visual Studio/Mono are detected on build agent. Previously you could refer to these properties as to system properties. Now we’ve changed it.

We decided to turn all these properties into configuration parameters, and therefore we’ve converted all refernces to such properties detected in TeamCity to keep builds running. However, it’s not possible to convert references used from a build script. To workaroud the issue you can add system property in build agent configuration or use compatibility mode switch in TeamCity properties:

• teamcity.dotnet.properties.compatibility.mode with value true
• dotNetPropertiesCompatibilityMode configuration parameter with value true in a build configuration settings.

Here is the list of changed parameters:

Note, there will no longer reported .NET Framework configuration parameters without explicit bitness (i.e. x86 or x64).

It’s about time to try a new TeamCity 6.0 EAP build, which introduces the long-awaited feature – Multiple Build Runners. Many of you voted for this one, and now we would like to hear your feedback on it. Here’s how it works – you can add as many build runners to a single build configuration as you need, and they will be executed step by step. In the end, the build gets merged status and the output goes into the same build log. If some step fails, the rest are not executed. We’re still actively develop this feature, so it’s up to you to help us make it better!


In addition to Multiple Build Runners, this EAP build contains various improvements for IntelliJ IDEA Project Runner, IntelliJ IDEA plugin, Eclipse plugin and more. Check the complete release notes and try the build, but don’t forget to back up your data before upgrade.

One more thing, there’s a new open-source plugin you might find interesting – Cloud-VMWare plugin, which provides an implementation of TeamCity cloud support for VMWare Player. Note, that this plugin is designed to work with the most recent TeamCity 6.0 EAP release, meaning this one.
Enjoy!

The JetBrains TeamCity Team

We would like to announce that today we’re opening Early Access Program for TeamCity 6.0.
Here’s a short summary for this EAP:

• TeamCity now treats more carefully builds that cannot start due to some configuration errors, for example when VCS repository is down on build start, or artifact dependencies can’t be resolved, etc.
• Agent-side checkout is now available for Perforce and ClearCase.
• Implemented new IntelliJ IDEA project runner.
• Swabra plugin is now bundled with TeamCity.
• We’ve added the long-awaited feature – build priority classes, which allow you to flexibly adjust the order of the builds in the build queue.
• Visual Studio Add-In was improved.
• Added VCS trigger rules for commit message.
• and more.

View the build’s release notes and complete change log, and try it.

Looking forward for your feedback!
Sincerely,
The JetBrains TeamCity Team