We are introducing build tags as means for organizing the builds. For example, we tag the builds that are released in the EAP.
In addition to marking builds with multiple tags, you can also filter builds in the history by clicking the desired tags.
This EAP release introduces a new feature that is aimed to address one of the shortcomings of a dedicated Continuous Integration server (multiple build agents in case of TeamCity): the necessity to login to a machine in the event that something goes wrong with the build. In addition to 1.0 version-old feature of killing the entire build processes tree right from the web UI, we are now providing means to investigate the issue: the ability to get the Java or .Net process thread dump right from the web UI!
Just click the link for the running build:
And a page showing the thread dump of the build processes(s) opens:
If the process is not Java or .Net, its command line is retrieved.
Please note that in this release Java thread dumps are supported only under Windows x86.
As the first step towards built-in search capabilities, searching by build number is now available:
The search results can be viewed either in a pop-up window or on a separate page.
If TeamCity queries multiple VCS servers, you can now specify specific usernames for each VCS root configured.
If your projects use several VCS roots you may benefit from new VCS trigger quiet period setting. This ensures TeamCity triggers a build only after a specified period for all VCS roots of the build configuration if there are no changes submitted to the VCS.
Using VCS triggering rules you can now prevent builds from being triggered after changes are made by a particular user or checked into a specific VCS root. This can be used, for example, to prevent build from being triggered when the process itself checks changes in.
The syntax is a bit tricky, but quite powerful.
If you use an RSS reader, you can now be notified about finished builds via a usual RSS feed (just make sure your RSS reader can access the server, and the status widget is enabled for the build configuration). Feed item text is generated using the FreeMarker template engine, and if you are not afraid looking under the bonnet, you can customize the feed to better suit your needs (adefault template sample is located in .BuildServer\config\default-feed-item-template.ftl).