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.
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.
Sequence of Builds: Same-sources Dependencies
Another major addition to TeamCity in this release is the new type of dependencies between the build configurations.
- display the depend-upon builds in the build results, in the build queue
- do not trigger a build when it has no pending changes (optionally)
- deal with failing depend-upon build (suggestions?)
Improved Change Log
Recently Failed Tests
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.
- in the Run Custom Build dialog you can now add or redefine any build property. The modified properties will be shown on "Build Parameters" tab of the build results;
- on pinning/unpinning a build you can now leave a comment;
- plugin packaged under .BuildServer can not have agent part that will be automatically transferred to agents. Packaging documentation;
- the requirement on synchronized clocks between TeamCity and Subversion servers has been lessened: now it only applies to the servers hosting externals-connected repositories.