TeamCity 6.5 is Here: New Features and Less Restrictive Free Edition

If you look through the What's New list of the release you are likely to see something useful for you.
We worked hard and we hope the release will make you a bit more happy with TeamCity and also with your builds.

The release both tweaks old things (like restyling web UI or renaming Responsibility into Investigation) and adds new strokes (like remote run on branches and test failures muting). These new directions are still to be fully explored and improved in the further releases based on your feedback.

Please make sure to look through the Upgrade Notes before you upgrade. It is recommended to test-drive the new version before upgrading your production TeamCity installation.

Our further plans are to start development of the next major version (TeamCity 7.0) and release updates to 6.5.x version with minor improvements and critical bug fixes if they surface.

TeamCity 6.5 RC: Days For the Official Release

Here is a build that is one tiny step before the official 6.5 release. It has just several bug fixes over the previous one and is meant to be the last chance to try a build before the release.

If you consider upgrading to 6.5, consider trying the build and warning us on any misbehavior found.

A hint: this build still has an EAP license bundled (valid for 30 days) so this can be yet another reason to download and try it :)

In the mean time we are starting to think what could we bring in TeamCity 7.0 and you might add your thoughts as well :)

TeamCity 6.5 Pre-Release: Less Restrictive Professional Edition and Stability Improvements

We are only  a small step away from 6.5 release and here is a build for you to try in your environment and let us know if anything goes wrong. The final 6.5 is planned to be released within a week or so.

Starting with this build we are dropping most limitations from Professional TeamCity edition except for the 20 build configurations limit. Now you can use per-project roles, any user authentication and more then 20 users in your TeamCity Professional installation.
As a professional user, you might be also interested in using more build configurations and here is a place to share your thoughts on this.


This build include a new way to install an agent onto a new machine: "agent push". Provided you have administrator credentials for a remote machine, you can now install a TeamCity agent on it right from "Agent Push" tab under Agents. The feature is in a bit "experimental" state, but we hope to improve it in further releases based on your feedback.

The build also further improves test muting and remote run on branches features as well as bundles PowerShell runner.

See more in the change log or full fixed issues list.

We ask you to try the build in your environment and let us know if anything goes wrong.

Get ready for the 6.5 release!

Responsibility Becomes Investigation. Are you an Investigator?

TeamCity has responsibility feature since the early days.

At first, it was introduced as an easy way to say to your buddy developers: "Hey, I've looked into the failure and I will try to fix it!". This was initially available only for build configurations but then was extended to individual test failures.

Then, we have got lots of request to allow assigning responsibility to other users. The reasoning is clear: I investigated a failure and figured out the dev who is to look into it. Now I want to ping him and let others know my findings right inside TeamCity UI.

But that is where social forces are brought into the play: we started to hear that many companies are not using "assign responsibility" because it sounds like blaming and the assigned party often gets a bit upset to say the least.


At that point we decided to rename responsibility into something other to reduce the "blame" impact. Choosing a good alternative took time and lots of considerations.
Finally, in 6.5 we are ready to introduce the renaming and are now using "investigation" instead of "responsibility".

One piece, though. How should we call a person who is investigating the failure?
Does "investigator" sounds right in the context? Should we stick with it or retreat to "assignee of the investigation"?
And we need your help here. Do you consider "investigator" a right term or not? Why?
Any alternatives you might suggest?

Please comment in the original issue or here.

Last EAP build before 6.5: Parametrized VCS roots, dotCover Add-in Integration and More

With current plans for 6.5 release in May we are publishing the latest additions to TeamCity and wait for your feedback. And there are lots to try and play with.

Parametrized VCS roots
You can now use %-references to TeamCity properties inside VCS roots. This opens a wide range of applications ranging from settings reuse between build configurations or builds in a chain to running a custom build specifying branch/tag on build start. Combined with ability to "publish" properties from a build and use them later via dep. references this unleashes power that is still to be understood.
Is your beloved case supported? Does it work as expected? Let us know!

Test muting improvements
We continue to improve test muting feature that allows to mark a test as not contributing to the build status.
Sounds interesting or scary?

Know your agents
If you ever wondered what agents have alike or differentiating environment, now you have a report to answer the question. Look under Agents / Parameters Report.
Did you manage to find something new about your agents?

And nobody should walk away empty-handed: there is a lot more in the build, including artifact dependencies on build tags and displaying failed tests grouped by package/namespace in UI.

See details in the change log or even dive deep into the fixed issues list.


Did I mention that your timely feedback is something that is really making TeamCity better?

TeamCity 6.0.3 Bugfix Update

The official download page has been updated to let you download 6.0.3 release with latest fixes for the stable TeamCity release.

Update is recommended for all users. Especially if you are using Perforce agent-side checkout, Maven or XML report import.

You can review the full list of fixed issues in our tracker.

Thank you all who reported issues against TeamCity 6.0 so we have ability to provide fixes for everyone.

In this particular update we introduced no new data convertors, so you can downgrade from 6.0.3 to any of 6.0.x versions just reinstalling/replacing TeamCity binaries and pointing them to the same .BuildServer directory.

In case you are a bit tired with a stable version and interested in what is coming in TeamCity 6.5, consider test driving our EAP.

TeamCity 6.5 EAP (build 17372): Mute Tests, AssemblyInfo Version Patcher, MSpec and More

Here is a new EAP build for the upcoming 6.5 release. The major additions include:

• Ability to mute tests. You can mute tests whenever you see a test name in TeamCity UI. The muted test still runs in a build, but it's failure does not paint the build red. Still to go is ability to automatically unmute the test after specified time or on successful test pass.
• Tests grouping. Failed tests are now grouped by package in most lists.
• .Net AssemblyInfo version injection. Need to add a version for your .Net assembly? Add corresponding build feature to scan the sources for AssemblyInfo files and inject build number into them before the build.
• MSpec support. You can now natively run MSpec tests in TeamCity, coverage support included.

For more detailed description see the release notes and full list of fixed issues.

As usual, we are waiting for your feedback on the new additions in this build so that we can adjust our development efforts for 6.5