|
||
| User Administration |
 |
 |
 |
Compass Version1.1
User AdministrationCompass is a fully authenticated web server, this means that in order to connect to Compass and view its web pages, you must log in as a user. The first user is created when installing Compass and is a site-wide administrator. All other Users and their access level are managed by site-wide administrators. There are three access levels for users:
Site-Wide Administrators have access to the administration and Script List page, while all other users do not. Users belong to projects and only have access to data and builds for the projects they have access to. Regular users have read-only access to their projects and can only view data and generate reports. Project Administrators have slightly higher permissions. Project Administrators can schedule new builds and create new build plans for the projects they have permission to access but they do not have access to manipulate data, upload files or generally have site-level access to the Compass Server. Each build that is run is initiated by a Compass user. If a build is scheduled to occur at a regular interval, then the user that scheduled the build is the user that is assigned to that build. If a repository revision change triggers a build, then Compass tries to figure out from the repository log, which Compass user checked in the code that caused Compass to start another build. If a user is not identified, then the user that created the build plan is assigned the build.
NOTE: Some installations of Compass have choosen to create just a single user account for each project and all members of the development team use the same account. Although this is provides the quickest set up of Compass it has some disadvantages. Mainly, users cannot be tied to their source-control client. Compass tracks when a user checks in code that introduced test- case failures or broken builds. If there is one Compass user for each repository user, then Compass can map it's users to the repository users and correctly identify which user chcked in each new revision. Setting up aliases is covered in another chapter, but it is important to note why an administrator may want to add each individual developer to the Compass Server.
User Administraton InterfaceThe User Administration section on the Administration page looks like this:  As you can see from the above image, the User Administration section consists of a table with a user in each row and buttons for creating new users and deleting selected users. Below we have subsections for each administrative action that can be taken for users: Add a New UserTo Add a new Compass user, click on the 'Create New User' button. This brings up the following Dialog:  In this dialog, simply add the user name, give the user a password and verify it, and select if the given user will be a site-wide admin, then click 'Create' Now, the new user we just added is in the user table. Delete Selected UsersTo Remove a user account from the Compass Server select the user you want to delete by clicking the checkbox in the user table in the row for that user. Then click the 'Delete Selected Users' button and the users will be removed. When removing users, Compass does not actually remove them from it's internal database. Compass does this to allow users to still be referenced on previously completed build plans, build output and build comments. It also provides more accurate graphing of user data in the charts section. Updating UsersIn the User List, each row has five columns. Below is an explination of each of the columns:
|
