TeamCity 6.0 RC2 (build 15700): Changes Filter in Schedule Trigger and Fixes

As one more bit before the release here is a RC2 build.

It has only several noteworthy changes and some issues fixed.

A little but wanted feature still slipped in at this time: ability to make Schedule trigger skip triggering a build if the pending changes match specific pattern.

Please note that this build comes without bundled EAP license key (but you can still get one form previous EAP build if you wish :).

Want to get a preview of the almost ready TeamCity 6.0? Jump on the train.

BTW, if you happen to still have TeamCity 4.x installed, you might want to consider buying an upgrade before 6.0 comes out (you can count days now). This way you can still get upgrade discount and get 6.0 and (as with a usual license) get all following releases within a year included into the price.

TeamCity 6.0 RC1 (build 15673): .Net coverage and other improvements

As the release is close we are trying to share the current TeamCity state more frequently with you.

The version has "RC" in the footer to denote close release, while we are still working on fixes and minor improvements.

This release moves Swabra settings out of the build step settings into a new place called "Features". The "Features" section will also get XML test reporter settings soon. This new section is designed to hold settings not specific to any particular build step, but participating in the build behavior.

If you have a plugin for TeamCity which affects build behavior but is not specific to a build step, you can consider moving plugin settings into the section. See the sources of the mentioned plugins for an example.

For this build's changes review, see the release notes or dive into resolved issues in the tracker.

As we are approaching release we are extremely interested in any upgrade and stability issues with this build.

Want to ensure seamless upgrade of your setup to final TeamCity 6.0? Try upgrading your data with a test installation of this RC.

PS I was a bit quick to announce some surprise feature in the previous EAP post. Unfortunately, we decided to postpone it till future releases since it will require some more work (and your feedback too!)

TeamCity EAP: Upgrade Confirmation, Bundled dotCover and More

This EAP build (#15638) is one of the last ones to have major feature additions before the upcoming TeamCity 6.0.

Our plans are to release 6.0 in about a month and now we are shifting our main effort to bugfixing and minor improvements. If you want to try new 6.0 features and give us feedback so that we can address it before the release, it's high time to grab the build and test-drive it in your environment.

If you are from .Net camp you can now start to collect code coverage with several simple settings configured from web UI. This is possible thanks to bundled JetBrains dotCover console tool. You can view coverage reports in TeamCity web UI before you decide to equip each developer with dotCover add-in for Visual Studio.

As to changes before 6.0, we have one more card in our sleeve that is likely to be exposed in one of the final EAP builds, so stay tuned.

Beware of the new upgrade confirmation screen that you will see upon first launch of  this TeamCity server.
Starting from this version TeamCity displays the current settings and allows to create backup of the data before proceeding. (Creating backup is only available if you upgrade from previous 6.0 EAP and any future builds)

Please check the settings are correct before proceeding (so that you do not point your test server to a production database by mistake).

This information is displayed only to authenticated users who have physical access to the server: can view TeamCity logs (logs/teamcity-server.log) and grab "Maintenance Authentication Token" from the log.

See the release notes for other major additions or look through full fixed issues list.

And please do not forget to let us know what you think.

TeamCity 5.1.5 Bugfix Update

Here is a fresh update for stable TeamCity versions: build 13602 available on the download page.

Included are several improvements in web UI and various fixes throughout the system. See our YouTrack installation for the full list.

This is a minor upgrade so you can probably do light version of upgrade (comparing to the full instructions).
This light approach is:

1. Create backup of your data from TeamCity Administration UI (backing up database and configuration data)
2. Install the updated TeamCity version over your existing one. The simplest way to do that is to:

• stop the server
• backup your <TeamCity home>/webapps/ROOT directory
• delete it's content
• unpack TeamCity-5.1.5.war (this is a zip archive) into the directory
• start the server

And consider trying 6.0 EAP as a test install to let us know how it suits your current or future needs!

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!