Jump to >

This documentation covers the in-development release of Review Board. You can see the latest stable docs or all previous versions.

Beanstalk Repositories

Review Board supports posting and reviewing code on Beanstalk repositories.

The following types of Beanstalk repositories are supported:

  • Git
  • Subversion

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.

Adding the Repository

To configure a Beanstalk repository, first proceed to add the repository and select Beanstalk from the Hosting type field.

Step 2: Provide Repository Information

Next, you’ll need to fill out the following fields:

Repository type:
The type of repository you’re adding. This can be either “Git” or “Subversion”.
Beanstalk account domain:
Your account domain (the one you specify when logging into Beanstalk). If you’re not sure, check your Beanstalk URL. It’s the mydomain in mydomain.beanstalkapp.com.
Repository name:
The name of your repository, as shown in your list of repositories.

Step 3: Choose a Bug Tracker

You can specify a bug tracker on another service. Beanstalk, at the time of this writing, does not provide one, but you can choose one on another service or provide a custom URL to your own bug tracker.

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). This is separate from Beanstalk’s own access controls.

Learn more about access control.

Step 5: Save the Repository

At this point, you should be able to save the repository. If saving succeeds, you’re done! You can start posting changes for review.

Configuring Repository Hooks

Review Board can close review requests automatically when pushing commits to Beanstalk. This is done by configuring a WebHook and pointing it to your Review Board server, and then referencing the review request in your commit message (which is done for you when using rbt land).

Let’s go over how to set this up.


Your Review Board server will need to be accessible over the Internet for this to work. Beanstalk will be performing HTTP/HTTPS requests to your server to notify Review Board of new commits.

Add the WebHook

First, log into your Beanstalk account and click on the repository you’re configuring. Then click Settings -> Integration. Then click WebHooks Classic.

../../../../_images/integrations-nav.png ../../../../_images/webhooks-classic.png

You’ll be prompted to enter the URL for your WebHook. You’re going to want to enter the URL to your server using a path in the form of /repos/repository_id/beanstalk/hooks/post-receive/, where repository_id is the numeric ID of the repository in Review Board (which you can find in the URL for the repository’s configuration page). For example, this might look like:


Save the hook, and you should be set!

Tag Your Commit Messages

To close a review request for a given commit, you’ll need to add some special text to your commit message that references the review request. This can be in the form of Reviewed at review_request_url or Review request #id. This must be on its own line, but can appear anywhere in the commit message.

For example:

Reviewed at https://reviewboard.example.com/r/123/


Review request #123

If you use rbt land, this will be automatically added for you when landing your changes.