Can assign user a role for every project.
This is the first public release that uncovers one of the major highlights of upcoming TeamCity 3.0: per-project user roles.
User can be assigned a "role" in any TeamCity project, or a global role (a role not specific to any particular project).
The set of available roles is fixed and is listed below.
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, etc.
Includes all actions available to "Project viewer" and additionally, can run/stop builds, run personal builds, browse file contents (withing 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.
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. Allows to edit all projects's settingsHas "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.
Existing users become developers for all existing projects. On upgrading (do not forget to backup your data before upgrade!), usual users will get "All projects developer" role assigned and administrators will get "System administrator" role.
Please note that users do will not get any roles in the newly created projects, so the role in the new project should be assigned to them . 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.
We are waiting for you feedback (mailto:) on the per-Project Roles and how they suit your daily needs!
Mark Sources by VCS Label
Supported are only CVS and Perforce. Feel free to request support for other version controls.
Ability to set the label for all or only for successful builds.
Duplicates and Inspections runner for Maven2 projects
Extended Processes Dump
In addition to Windows support introduced in previous EAP release (Java and .NET processes), we are adding support for Linux with 1.5+ JDK (any other platform that has jstack Java utility that is usually included into JDK should be supported too).
UI is also improved featuring build processes tree.
- Setting the frequency of querying the version controls for changes (adjustable on server-wide or single VCS root levels)
- Ability to request immediate changes checking
- Administration page with the list of all VCS roots configured in the TeamCity.
- Search by tags and project/Build configuration names
- RSS feeds can now be generated only for failed/successful builds and with changes of particular user. See feed "customize" link on My Settings and Tools page.
- Remote run support for StarTeam, ClearCase and Visual Source Safe from IntelliJ IDEA.
- Support for different URLs for accessing SVN server from server and IDEs (no configuration required)
- TFS communications performance is improved