Preferences
The Preferences page provides access to display and usability options.
Watched Repositories (Projects)
Note: Gerrit Code Review often uses the term “Project” to refer to a repository. AccuRev uses the terms “repository” or “repo” when referring to a repository, and reserves the term “project” when referring to specific Gerrit functionality, or when referring to some kind of planned or defined undertaking.
The Watched Repositories page allows you to identify the repositories whose changes you want to track. Click the
Add button to add a repository to the Watched Repositories page and to optionally configure Gerrit Code Review to send an email notification whenever a change occurs in that repo. When adding a repo, use the
Browse button to navigate to the repo of interest. If you want to specify conditions under which you want to be notified of a change (perhaps you are interested only in changes to a specific branch, for example), see the
Searching Changes topic in the Gerrit Code Review documentation to learn more about search operations and search expression syntax.
Contact Information
Enter the name of the currently logged-in user. You can register multiple email addresses for this user, but only one can be specified as the “preferred” address. Gerrit uses the preferred email address when it needs to generate an email address for you; it uses others to validate incoming email to you.
Tip: GitCentric accepts mixed-case values in the email address domain. For example, both johndoe@AcmeCo.com and johndoe@acmeco.com are valid email addresses.
Public Keys
You must configure SSH public key authentication before you can upload changes.
If you already have an SSH key:
Click Add and paste the contents of ~/.ssh/id_rsa.pub into the resulting Paste the public SSH Public Key below: field. Make sure that you do not introduce line-breaks when copy & pasting.
If you need to create an SSH key:
1. If necessary, install ssh-keygen (this is normally included as part of a Git or O.S. installation).
2. > ssh-keygen -t rsa -C "<yourEmailAddress>@<yourDomain.com>"
For more detailed information about SSH keys, see
Create an SSH key on page 14, or follow the link on the dialog box.
AccuRev Servers
You use the AccuRev Servers page to associate a GitCentric user account with an AccuRev user account. You need to use this page only if you have multiple AccuRev servers in your environment. Otherwise, the GitCentric<-->AccuRev user account association is managed automatically, as part of the self-registration process. (See
Register with GitCentric on page 16 for more information on self-registration.)
Note: Although the UI does not enforce this, you should not specify multiple user accounts on the same AccuRev server here. If you specify more than one user ID on the same server, GitCentric may default to one that you did not intend. It is fine to specify multiple servers here, with one user ID each.
To specify a GitCentric<-->AccuRev user account association:
1. Click the Add button.
2. On the panel that appears:
a. Select the server from the AccuRev Server drop-down list.
b. Enter your username on that server in the AccuRev Username field.
The AccuRev user on this server that you use for GitCentric functions. If you are an administrator, this might be an account like acserver if you have legacy AccuRev systems. See the GitCentric Installation and Release Notes for a discussion about this user account.
c. Enter the password associated with that username in the Password field.
4. Click the Save button to register the account.
HTTP Password
Some environments do not permit you to use SSH to connect across a firewall. If you cannot use SSH, but you can connect to the server with smart HTTP, you can generate a password here, and then access your Git repositories with a URL constructed with “...p/<repository>”.
Note: GitCentric supports only Git “smart HTTP” not so-called “dumb HTTP”. Smart HTTP is documented on several Git-related sites.
The syntax to clone a repository with smart HTTP is:
git clone http://<username>:<password>@<host>:<port>/p/<repository>
Example:
git clone http://testuser:PaoYhDp8BFoA@localhost:8100/p/TestProj2
Once you have cloned, you can pull / push over HTTP just like you can over SSH.
Avoiding Password Entry
Generated passwords can be difficult to memorize, and providing one each time you connect using HTTP can be a nuisance. Fortunately, Git provides a number of mechanisms to help deal with this.
First, you can create a .netrc file in your home directory (“_netrc” if you are using msysgit on Windows). For example:
machine localhost
login testuser
password PaoYhDp8BfoA
The .netrc file lets you keep the <username>:<password> out of the URL for enhanced security, but it is still stored as plain text.
A more secure approach, if you are using Git 1.7.9 and later, is to use Git’s credential helper, which tells Git to store your password in cache for 15 minutes:
git config --global credential.helper cache
You can increase the timeout by specifying the desired limit in seconds. This example shows the timeout set to 30 minutes:
git config --global credential.helper "cache --timeout=1800"
Use --unset to revert to specifying the password manually:
git config --unset credential.helper
People
This is a read-only display of the security groups to which the logged-in user belongs. To create or modify groups, go to
Administration -> Groups in the Web GUI. For details about how groups are implemented, see the
Gerrit Code Review documentation. For “How to” information about managing groups in the GitCentric context, see
Manage GitCentric Groups on page 49.
