Distributed Build Management and Continuous Integration Server

Web UI

Take care of all the administrative tasks using TeamCity's web interface:

• set up your projects and build configurations as easy as one-two-three
• copy/clone projects and build configurations
• manage Build Agents' properties and compatibility
• view and edit version control system settings used by TeamCity
• specify per-project access rights and permissions
• select the build history clean-up policy
• manage a number of TeamCity server properties which are going to be applied for all projects and users, such as server configuration, and notifications settings
• Option to preserve or clean artifacts of builds used in artifact dependency Also, cleanup rules configuration UI was enhanced.

Per-project Access and Roles

We have introduced server-wide and per-project roles so you can now control access to TeamCity's features with role-based security:

• A System Administrator has full control over all of TeamCity's features
• A Project Administrator has permission to modify the project's configuration, change user roles on projects, manage Build Agents, and perform all the tasks available to project developers
• A Project Developer can run and stop builds, manage the builds queue, tag builds, take responsibility, view the content of modified files, label builds and more
• The Project Viewer role suits the needs of a non-committer who just monitors the projects' status; they cannot run builds
• A Build Agents Manager can change an Agent's run configuration policy and enable and disable Agents

Guests in TeamCity Professional edition now do not have access to the Build Agent details page. The same is true for the "Project Viewer" role in Enterprise edition.

Depending on your company's needs or policy, you can assign one or several roles in different projects to a single user.

TeamCity Professional Edition only supports guest, administrator and user roles and does not support per-project roles assignment.

User Management (LDAP, Domain, and Guest Accounts)

TeamCity supports several authentication schemes:

• Default Authentication (cross-platform)
• NT Authentication (cross-platform)
• LDAP Authentication (cross-platform)

You can customize guest access to TeamCity, which can log in without authentication,and edit the roles which guest users can have.

On the user accounts page you can now search for users by keyword or by their roles.

TeamCity Professional Edition only supports the Default Authentication and does not support guest user roles assignment.