Setting-up-Gerrit

Setting Up Gerrit

How to get started – Gerrit registration

1. Create an account in the Qt bug tracker [bugreports.qt.io] (also known as JIRA)
2. Go to https://codereview.qt.io and log in with your Qt bug tracker credentials
   • Note: Gerrit usernames are case-sensitive, but JIRA usernames are not. If you attempt to log into Gerrit with different capitalizations, you will end up with multiple accounts.
3. Go to the Settings page: https://codereview.qt.io/settings/
4. Go to “Settings” -> “Contact Information” and register your email address. You will receive a confirmation email; click on the link inside to finalize your registration.
   • Note: Your username and e-mail address will be visible to the public. Use an alias + a custom e-mail address if you want to stay anonymous (this is discouraged)
5. Go to “Settings” -> “SSH Public Keys” and upload your public SSH Key [help.github.com] , configure username (under contact information), upload public SSH key [help.github.com]
6. If you are behind a firewall that blocks SSH access:
   1. Go to “Settings” -> “HTTP Password”
   2. Click “Generate Password”
   3. Add the following line to your

      ~/.netrc
      

      (Windows:

      ​%USERPROFILE%\_netrc
      

      ):
      

Local Setup

Configure SSH properly (the URLs below rely on this). Add this to your

~/.ssh/config

(Windows:

C:\Users\%USERNAME%\.ssh\config

):

NOTE: The following steps need to be applied to every clone:

Install the hook generating Commit-Id files into your top level project directory, as well as all sub-repositories (e.g. qtbase.git) either through

or by downloading the file via browser: commit-msg [codereview.qt.io] and putting it into the

.git/hooks

directory (make sure it is executable).

It is recommended to install the git_post_commit_hook from the qtrepotools [qt.gitorious.org] repository. This gives you the checks of the Sanity Bot locally. To do this, save the script
into each <path to git clone>\.git\hooks\post-commit

NOTE: Starting with git 1.7.8, if

<module name>/.git

contains

gitdir: ../.git/modules/<module name>

, you need to put the submodule hooks in

.git/modules/<module name>/hooks

instead of

<module name>/.git/hooks

.

Configuring Git

We are developing in a heterogeneous environment with both Unix and Windows machines. Therefore it is imperative to have all files in the repository in the canonical LF-only format. Therefore, Windows users must run

to automatically get CRLF line endings which are suitable for the native tools, and Unix users should use

(this is a safety measure for the case where files with CRLF line endings get into the file system – this can happen when archives are unpacked, attachments saved, etc.).

To be able to create commits which can be pushed to the server, you need to set up your committer information correctly:

Please do not use nicknames or pseudonyms instead of the real name unless you have really good reasons.
Gerrit will not accept your commits unless the committer information matches the email address(es) you registered.

To facilitate following the style guide for commit messages, it is recommended to install the Qt commit message template:

A common mistake is forgetting to add new files to a commit. Therefore it is recommended to set up git to always show them in

git stat

and

git commit

, even if this is somewhat slower (especially on Windows): Git has a somewhat stupid default that

git push

will push all branches to the upstream repository, which is almost never what you want. To fix this, use:

This is not relevant for mainline branches under Gerrit control, as all pushing happens with refs anyway, but it may be important for your private clones.

Sometimes it is necessary to resolve the same conflicts multiple times. Git has the ability to record and replay conflict resolutions automatically, but – surprise surprise – it is not enabled by default. To fix it, run:

git pull

will show a nice diffstat, so you get an overview of the changes from upstream.

git pull —rebase

does not do that by default. But you want it: To get nicely colored patches (from

git diff

,

git log -p

,

git show

, etc.), use this:

Git supports aliases which you can use to save yourself some typing. For example, these (any similarity with subversion command aliases is purely accidental ;)):

Using Existing clones

Add a

gerrit

remote pointing to codereview.

If you are behind a SSH-blocking firewall, use the https protocol:

For Qt 4.8, use

If you are behind a SSH-blocking firewall, use the https protocol:

Cloning repositories

You should clone from the repositories hosted at qt.gitorious.org [qt.gitorious.org] or github.com/qtproject [github.com] and track changes from there in order to keep the load on Gerrit down.

Cloning Qt4

For qt.gitorious.org [qt.gitorious.org] :

For github.com/qtproject [github.com] :

Note that Qt4 does not have a

master

branch (since no 4.9 is planned). So, you should push changes to the

4.8

branch.

Cloning Qt5

For qt.gitorious.org [qt.gitorious.org] :

For github.com/qtproject [github.com] :

It is recommended that, regardless of the server you use for the initial clone, you use the init-repository script in qt5 to set up the gerrit remote(s) pointing to codereview, and to clone the submodules.

Alternatively, individual Qt5 submodules can be manually cloned as well. Follow Using Existing Clones above after cloning.

Note that Qt 5 submodules have been changed from absolute to relative URLs (like “../qtbase.git”) in the .gitmodules file.
If you make a clone of git://gitorious.org/qt/qt5 in gitorious as git://gitorious.org/~<username>/qt/<cloned-repository-name>.git the init-repository script will not work.

A URL rewrite rule has to be added to the .gitconfig file:

Cloning Qt Creator

For qt.gitorious.org [qt.gitorious.org] :

For github.com/qtproject [github.com] :

Pushing your local changes to gerrit

After you have committed your changes locally, you can push them to Gerrit like this (for example,

5.4

branch):

You can’t push directly to a branch. So you need to create a review. “refs/for/5.4” means “please submit this as a review for branch 5.4”.
It is recommended you use the git-gpush script from the qtrepotools repository [qt.gitorious.org].

Categories:

• Developing_Qt
  • Instructions