Monday, October 18, 2010

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/ file and add a line into it:
<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 "" 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.

Wednesday, October 6, 2010

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.