We have significantly modified TeamCity user interface in this EAP build, and we encourage you to share your feedback on it with us.
Starting with this EAP, TeamCity Administration page has a new look which was designed to meet several requirements, such as:
When a failed test's stacktrace is expanded you can not only see the stacktrace itself, but also details about first failure of this test in this build configuration:
The same information is shown on Current Problems and Investigation pages as well. Note that if test fails in more than one build configuration you can see all of them:
We decided to always show check boxes near test names instead of asking user to switch to bulk mode explicitly.
While staying on build log sometimes it is necessary to see build summary, now you can easily access it from each build tab.
On build configuration home page there is a check box which enables showing of changes from dependencies. If enabled, this setting affects all of the pages where build configuration changes are shown, i.e:
We significantly improved usability of typed parameters, as well as added new parameter types.
Currently you can use the following types:
Note: values of password parameters will be hidden from build log, and from Build Parameters tab of the build. Also it is impossible to see values of these parameters in custom build dialog. In configuration files such parameters are stored in scrambled form.
All parameters support a number of common properties, such as:
do not show parameter in custom run dialogoption - if set, this parameter will be hidden from custom run dialog
request user confirmation for parameteroption - if set, then custom build dialog will be shown on each manual build triggering, allowing to review parameters, which should be sent to a build
Plugin providing information about agent hardware was available for quite some time (see http://youtrack.jetbrains.net/issue/TW-4857). We decided that it is useful enough to bundle it with TeamCity distribution.
The plugin provides several parameters:
teamcity.agent.hardware.memorySizeMb- agent physical memory
teamcity.agent.hardware.cpuCount- number of CPUs (cores) on agent
teamcity.agent.work.dir.freeSpaceMb- available free space in Mb on a disk where agent work directory resides, updated on every build finish