Build Sequence Improvements
Here are the most notable advances in the new type of dependency. (BTW, can you propose a good name for it apart form "dependency by sources"?):
Option to reuse already finished builds
A dependency can be configured to always force a build triggering or use already finished build as dependency (provided there are no pending changes in the build configuration).
Consider build A source-depending on build B.
When "Take already started build with same revisions" is not checked in the dependency form A to B, B will always be re-triggered when A is triggered. This is useful if B performs some build preparation steps that should always be run.
When "Take already started build with same revisions" is checked, B will only be triggered when it has pending changes. Otherwise, a version of B already in the history will be used.
Artifact dependency on build form the "builds sequence"
If you want to use artifacts from the build you are depending on, just choose "Last finished build" option f the artifact dependency and the dependency build will be used as a source.
Displaying use dependencies for the finished builds
The source-dependencies are now shown on the "Dependency" tab of the build results
Personal builds for the build sequences
If you initiate a personal build for a build that source-depends on others, all the dependency builds will be triggered.
Please note that in this EAP release the pre-tested commit status is determined on the build directly run, the statuses of its dependencies are not yet considered.
Test Details Page
Now you can browse the history of runs of a particular test. Click on the test name in the build results overview or in the build tests tab and you will get to the test's details page that features timings data, test duration chart and list of the test runs with corresponding build details. We are still in the process of determining the necessary level of detail to present on the page and brushing it up. Any comments to the current version are welcome in the forums!
.Net users can now benefit from integration with FxCop. Once you install the tool on the build agents and configure a new build configuration, the results can be browsed in the same Code Inspections browser that TeamCity has for Java.
Here is the settings screen:
Pre-tested Commit if no New Tests Failed
IDEA and Visual Studio plugins now have ability to trigger pre-tested commit that will be committed if the builds do not have any new failed tests. This option can help if some tests in the build are failing but you still need to use the delayed commit feature. Please note that for this feature to work properly the build should continue and run all the tests even if some have failed. Support in the Eclipse plugin is under way.
- Service messages now support reporting test duration, each messages can have timestamp and flowId, requirements to start and end service message with a newline has been removed. For the details, please refer to the updated documentation section.
- Changes popup now sorts changes by time (not by user) for History builds
- More properties are now supported in the VCS labeling pattern. Build number now supports limited set of property references via "%system.<property_name>%" syntax.
- "Run personal build on agent" feature for Eclipse plugin
- "Open Remote Desktop" action for Windows agents. The feature was already present in the previous EAP release, but now we made it a fully-fledged plugin, so other plugins can be written to extend agent details page.
- Important messages of the build log now try to show all the errors even if there are many warnings before them
- Tests suites are now handled more accurately: they are displayed in web UI and the same test in different suites is treated as different tests. Please note that if you have a suite name set, the full test name will change and this will cause TeamCity to treat the test as a new one (not related to the test in builds built with earlier TeamCity versions). Thus, test history can start from scratch for these tests.
- Ability to assign personal build to a specific agent from Eclipse and Visual Studio plugins
- New types of agent requirement added to allow versions comparison. It can handle various formats of product versions like 1.6.0_02-b06 and others. Actually, try to provide an example of a version format it cannot handle (this should be a a pretty hard task ;)