Review Board supports posting and reviewing code on Git repositories.
Unlike most types of source code management systems, Git has a very limited remote protocol, which isn’t capable of some of the requests Review Board and other similar tools require. Because of this, if Review Board does not have local file-based access to your main Git repository, you will need to set up a wrapping service, such as GitWeb or cgit. This is covered in more detail later in this guide.
To simplify posting changes to Review Board, we recommend using RBTools. This ensures that the diffs are in the correct format, and makes managing review requests much easier. See Using RBTools with Git for more information.
This guide assumes that you’re adding a Git repository that’s hosted somewhere in your network or one that’s accessible by your Review Board server. Review Board requires either local access to your repository or network access using a wrapping service (as documented below).
Follow the documentation in the links below if your Git repository is hosted on one of these services, as configuration will differ.
- AWS CodeCommit
- Bitbucket Server
- Fedora Hosted
- GitHub Enterprise
If your Git repository is hosted on another third-party service, it will not work with Review Board! Please contact us to request support for that service.
Installing Git Support¶
Before you add the repository, you will need to install the git command line tool in a system path (or in a place accessible by your web server’s process). This can be installed through your system’s package manager.
See the installation guide for Git.
Adding the Repository¶
To configure a Git repository, first proceed to add the repository and select Git from the Repository Type field.
If your repository is locally accessible over the file system via the Review Board server, you can point to file path of the repository. However, there are caveats. See Using a Local Clone.
Using a GitWeb-Backed Repository¶
If you’re self-hosting one or more Git repositories, you can install GitWeb and use it as a form of remote API for Review Board. This will give you basic support for posting and reviewing changes (though some features, like browsing for commits on the New Review Request page, will not work).
Once you have GitWeb set up, you will want to set your Path field to the main clone path of your repository. If you use both HTTPS and SSH access to your repository, set one in Path and the other in Mirror Path.
If you’re using an SSH-backed repository, you will need to configure a SSH key in Review Board, and grant access on the repository.
You will then need to set the Raw File URL Mask field to point to a specific URL on your GitWeb server. This field essentially specifies a URL template that Review Board can fill in with a filename and Git blob SHA that will return the contents of that file and blob. This should take the form of:
For example, if your repository is configured in GitWeb as
projects/myrepo.git and your GitWeb is at
git.example.com, you will
want to use:
Using a cgit-Backed Repository¶
One alternative to GitWeb would be to install cgit. This works similarly to GitWeb, in that it will make use of the Raw File URL Mask field.
Follow the instructions in Using a GitWeb-Backed Repository, but use the following for the URL mask:
For example, if your repository name is
myproject and your server name is
git.example.com, you would use:
Using a Local Clone¶
Review Board can make use of a locally-accessible Git clone, so long as that clone contains the very latest changes for your repository. This is an easy way to configure a Git repository accessible over the filesystem.
If the Git clone is the master repository that your developers are cloning from, then you’re in good shape. However, if it’s a clone of the master repository, you will need to ensure it’s consistently up-to-date. One way to do this would be to have a cron job pull the latest changes at least once a minute.
When using a local clone, you’ll need to point the Path field to
.git directory within your clone. For example:
The Mirror Path field should then list the URL that developers would normally clone from. This is usually a HTTPS or SSH-backed URL. It’s important to note that you can only list one (which should not normally be a problem if you’re using RBTools with name-based repository lookups, which we recommend by default).
To get the clone URL, you can run:
$ git remote show origin
Then use the value shown in
You will leave the Username and Password fields blank.