The most of the features in this build are brand new and we need your feedback on how do you find them, how they match your use cases and what improvements do you want in them.
From now on we have a little time-machine built into TeamCity. Just choose a change in the Custom Run dialog and TeamCity will trigger a build getting the sources corresponding to the change in the past.
You can also locate a change in the build's changes and trigger a build from there.
As with any time machine, there are some tricky issues:
Caution: the builds in the history are sorted by the start time, not changes.
For the history builds, you can see "History" instead of "Changes" and the build info is rendered using italic.
Please note that the history build always uses the VCS roots and settings currently actual in the build configuration. Particularly, if you delete a VCS root from a build configuration you will lose ability to trigger history builds with changes of that root.
Another major addition to TeamCity in this release is the new type of dependencies between the build configurations.
It allows you to ensure that a build will start only after the one it depends from is run and finished. Moreover, TeamCity ensures the builds use sources corresponding to the same moment.
Here is how it works:
This same-sources dependency is configured in the "Dependencies" section of the Build Configuration settings under "Dependencies by Sources".
Some time ago we started to gather recent tests failures statistics for the Tests Reordering feature. Now you can see this statistics in the web UI:
3.x release searched builds only by project, build configuration name, agent, tags and build numbers
Now builds also can be found by build status text, change committer and comment, VCS label, name of the triggerer. In addition you can use wildcards (?, *) and more. The search is powered by Lucene now.