Easy Access to GitHub Commit Page from TeamCity

(inspired by the tweet)

If your TeamCity is watching GitHub repo, you can add a link to GitHub commit page from every change displayed in TeamCity. The feature to allow that is called external changes viewer.

This requires some config file editing effort, but don't be scared:
Locate .BuildServer/config/change-viewers.properties file and add a line into it:

<NN>.changeSetUrl=http://github.com/<user>/<repository>/commit/${changeSetId}

Where:
<NN> - internal TeamCity id of the VCS root used. You can get the id if you open VCS root editing page in TeamCity and find "&vcsRootId=<NN>" in the URL.
<user> and <repository> - parts of GitHub repository URL.

See detailed description of the format in the comments inside "change-viewers.properties.dist" file.

Once you save the file (no TeamCity restart is required), all the changes of the VCS root affected should get icon that you can click to open GitHub commit page.

Like the feature? Let us know about this in the forums and suggest improvements in our issue tracker so that we can further enhance it.

TeamCity EAP: Collapsible Build Log, Gradle Support and More

This EAP build continues improvements in redesigned My Changes page and IntelliJ IDEA project runner while also adds several new features like build log displayed as a collapsible tree (wow, that was the very second feature filed for TeamCity project), Gradle runner (in experimental status) and ability to display some server-wide usage statistics (see Server Configuraiton/Usage Statistics).
Grab the build as usual.

If you are keen on details, then full report from our issue tracker is for your service.

It probably makes sense to install the build as a test server and try upgrading data of your main server to see how it goes.

Several notes on the things that have been changed and might affect your installation:

• if you relied on automatically defined system.DotNetFramework* properties, they are no longer available as system.* properties, but rather as properties with no prefix/configuration parameters (and so they are not automatically passed into your build script).
• NUnit and MSTest settings are now extracted into separate runners
• several data structures got more fields in REST API
• open API on agent was adopted to allow for multiple build steps

 
With our monthly pace with EAP builds this is one of the last EAP builds before TeamCity 6.0 which we plan to release in several months. So if you are interested in any of the 6.0 features (see the change log) do not postpone trying the build so that your feedback can still contribute to 6.0 release.

TeamCity 6.0 EAP: New My Changes Page, Filtering Controls and More

Want to try new features? We hav'em!

The latest EAP build of TeamCity 6.0 (build 15400) adds:

• revamped My Changes page (love or hate it? Let us know!);
• new UI controls powered by jQuery to ease your input: filtering drop-downs and calendar chooser. Keyboard navigation in "Projects" popup as a bonus;
• assign responsibility for a group of tests in a single action;
• ability to re-run failed tests in Visual Studio plugin (requires installed ReSharper that you have probably  already installed anyway);
• improvements in IntelliJ IDEA/RubyMine/PyCharm plugin;
• and more.

Try is and tell us what you think!

TeamCity 5.1.4 Bugfix Update

We've just published a bugfix update for TeamCity: version 5.1.4 (build 13550).

This release contains fixes for various issues uncovered throughout the system, and introduces minor improvements.

Please consider upgrading especially if you use TeamCity with Subversion, Git, EC2 cloud agents integration, RSpec 2.0 or Visual Studio add-in.
This release also adds transparent reporting for tests run by Maven Failsafe plugin.

See the full issues list in our tracker.

Get it from the official download page.

If you like living on the cutting edge, consider upgrading to TeamCity 6.0 EAP build which contains lots of improvements and new features over TeamCity 5.1.x.

Next TeamCity 6.0 EAP build: 15311

For those of you who like to live on the cutting edge, here is one more piece to try: build 15311 of 6.0 EAP.

What's in it?

• Multi-step build configurations AKA "multiple build runners"
• Java coverage display in Eclipse plugin
• Ability to execute IntelliJ IDEA JUnit/TestNG run configuration after IDEA project compilation
• and more

We especially need your feedback on the new features so if you try the build please do not hesitate to let us know how well they suit your needs.

P.S. This EAP release is also compatible with experimental VMWare integration plugin that we just published.

5.1.3 Bugfix Update is out

Recently, we've published a minor release 5.1.3 with several bug fixes.

Just to name a few, server cleanup times were improved in case of many builds with artifact cleanup level configured and a number of Visual Studio plugin exceptions were fixed.

Update is recommended to all users.

Please review the fixed issues, download the build and upgrade.

TeamCity 6.0 EAP is Open

It's been several days since the first EAP build of upcoming TeamCity 6.0 is live.

The changes page pretty much describes it all.

Along with improvements like separate status for the builds that did not actually start the build process and agent-side Perforce checkout, there are new features like completely new runner for IntelliJ IDEA projects (supporting IDEA artifacts building) and build configurations' build queue priorities.

The last one has experimental status and we might rethink the approach based on your input. Please let us know how well it matches your needs and how easy you find it to use.

The EAP should be pretty stable as we run the trunk version of the server internally for quite a while already. However, as always please mind pre-beta state and experimental status for the new features. TeamCity 6.0 is planned for the end of this year, and we want to hear from you on the features so that we can rework or polish them to match our audience.

Sorry for the late announcement here, but it takes some time to keep up to the team's pace being on vacation :)