The set of available roles is fixed and is listed below.. Here is the list with a brief description:
Can view the builds of a project, browse build results including artifacts and list of changes (but not file content), set notifications for the project, view queued builds of the project, etc.
Includes all actions available to "Project viewer" and additionally, can run/stop builds, run personal builds, browse file contents (withing via web diff view), reorder the build of the project in the queue, browse build configuration settings.
Includes all actions available to "Project developer" and additionally has access to administration area where such user can change settings of the project, create/delete and change settings of project's build configurations, set-up clean-up rule for the project's build configurations.
All projects viewer
Global role. Analogous to "Guest" access in older versions. The same as "Project viewer", but can view all the projects in the system.
All projects developer
Global role. Has "Project developer" access to all of the projects in the system.
Global role. Allows to enable/disable agents.
All projects administrator
Global role. Has "Project administrator" access to all of the projects in the system, can create and delete projects, manage VCS roots shared between projects. Includes "Agent manager" role.
Global role. Includes "All projects administrator" role. All administration tasks are available for this role.
Please note that users will not get any roles in the newly created projects. If user does not have "All projects viewer/developer" role, please do not forget to assign the necessary roles via user's profile page for the users that need access to the project.
Stay tuned for the more powerful UI to ease group operations for assigning user roles.
Test-level Duration Charts
In addition to the list of unit tests run in a build, you can now view any test duration across the builds via a chart available in the tests list:
Ability to Mark Sources by VCS Label
You can instruct TeamCity to put a label to the version control for the sources used in the build. See Version Control Settings page of a build configuration settings. Available options are whether to mark all or only successful builds and label format that can include the build number.
Supported version controls are
CVS and Perforce. Feel free to request support for other version controls.
Duplicates and Inspections runner for Maven2 projects