Review Board 5.0 Documentation

Need help? Talk to us today about a support contract!

Jump to >

Cliosoft SOS Repositories

Review Board supports posting and reviewing code on Cliosoft SOS repositories, enabling your team to review code or other files across all of your projects.

RBTools is used to take your pending changes in a workarea and put them up for review. This is a collection of command line tools that simplifies working with Review Board. See Using RBTools With Cliosoft SOS for a guide on how developers can use RBTools to manage their review requests.

Requirements

On the Review Board server:

On developer machines:

  • SOS 7.20 or higher, with a valid license.

  • RBTools 3.1 or higher, used to post changes for review.

Adding the Repository

You will need to complete these steps for each SOS project you want set up in Review Board.

To get started, add a repository and then select Cliosoft SOS from the Repository type field.

Step 1: Fill in the SOS fields

You will need to tell Review Board where your SOS installation is, which license you want to use, and which SOS server and project this repository will map to.

You can specify these with the following fields:

SOS installation directory:

The absolute path to the SOS installation on the server.

This is equivalent to CLIOSOFT_DIR environment variable.

SOS license:

The absolute path to the license file for this installation, or the port and host for the license server.

This is equivalent to the CLIOLMD_LICENSE_FILE or LM_LICENSE_FILE environment variables.

SOS server name:

The name of the SOS server where the project resides.

SOS project name:

The name of the SOS project that this repository will map to.

Step 2: Choose a Bug Tracker

You can specify a bug tracker where any bug numbers will link to.

Review Board provides a built-in list of bug trackers, but you can also set a URL to any additional bug tracker you want to use.

Learn more about bug tracker configuration.

Step 4: Manage Access Control

You can now choose who should have access to this repository (both posting against it and viewing review requests posted against it).

Note

This is separate from any access controls defined in SOS! If you need to limit SOS project access to individual teams or users, you will need to configure access control lists in this repository.

Learn more about access control.

Step 5: Save the Repository

At this point, you should be able to save the repository by clicking Save.

If saving succeeds, you’re done on the Review Board side! Let’s set up RBTools.

Step 6: Setting Up RBTools

You’ll need to set up RBTools to map the project to the repository on developer machines. The best way is to configure a .reviewboardrc file in the SOS project, making it available for everyone to use.

Place the following in this file:

REVIEWBOARD_URL = 'https://<server>/'
REPOSITORY_TYPE = 'sos'
REPOSITORY = '<configured repository name>'

You can click RBTools Setup beside your new repository in the repository list page to get some sample lines. Make sure to include REPOSITORY_TYPE along with this!

Now that you’re set up, learn how to use RBTools with SOS.