• Get Review Board
  • What's New
  • Products
  • Review Board Code review, image review, and document review
  • Documentation
  • Release Notes
  • Power Pack Enterprise integrations, reports, and enhanced document review
  • Try for 60 Days
  • Purchase
  • RBCommons Review Board as a Service, hosted by us
  • Pricing
  • RBTools Command line tools and Python API for Review Board
  • Documentation
  • Release Notes
  • Review Bot Automated code review, connecting tools you already use
  • Documentation
  • Release Notes
  • RB Gateway Manage Git and Mercurial repositories in your network
  • Documentation
  • Release Notes
  • Learn and Explore
  • What is Code Review?
  • Documentation
  • Frequently Asked Questions
  • Support Options
  • Third-Party Integrations
  • Demo
  • Review Board RBTools Power Pack Review Bot Djblets RB Gateway
    1. RBTools 5.x
    2. Version 5.x
    3. Version 4.x
    4. Version 3.x
    5. Version 2.0
    6. Version 1.0
    7. Version 0.7
    8. Version 0.6
    9. Version 0.5
    10. RBTools Documentation
  • Home
  • Installing RBTools
  • rbt Command
  • Configuration
  • Authenticating to Review Board
  • Repository Configuration
  • Per-User Configuration
  • Team Foundation Server Configuration
  • Commands
  • alias
  • api-get
  • attach
  • clear-cache
  • close
  • diff
  • install
  • land
  • list-repo-types
  • login
  • logout
  • patch
  • post
  • publish
  • review
  • setup-completion
  • setup-repo
  • stamp
  • status
  • status-update
  • RBTools Workflows
  • Using RBTools With Cliosoft SOS
  • Using RBTools with Git
  • Using RBTools with HCL VersionVault and IBM ClearCase
  • Using RBTools With Perforce
  • RBTools Python API
  • Overview of the Python API Client
  • Tutorial
  • Resource-Specific Functionality
  • Module and Class References
  • rbtools
  • rbtools.deprecation
  • rbtools.api
  • rbtools.api.cache
  • rbtools.api.capabilities
  • rbtools.api.client
  • rbtools.api.decode
  • rbtools.api.decorators
  • rbtools.api.errors
  • rbtools.api.factory
  • rbtools.api.request
  • rbtools.api.resource
  • rbtools.api.transport
  • rbtools.api.transport.sync
  • rbtools.api.utils
  • rbtools.clients
  • rbtools.clients.base
  • rbtools.clients.base.patch
  • rbtools.clients.base.registry
  • rbtools.clients.base.repository
  • rbtools.clients.base.scmclient
  • rbtools.clients.errors
  • rbtools.clients.bazaar
  • rbtools.clients.clearcase
  • rbtools.clients.cvs
  • rbtools.clients.git
  • rbtools.clients.mercurial
  • rbtools.clients.perforce
  • rbtools.clients.plastic
  • rbtools.clients.sos
  • rbtools.clients.svn
  • rbtools.clients.tfs
  • rbtools.config
  • rbtools.config.config
  • rbtools.config.loader
  • rbtools.diffs
  • rbtools.diffs.patches
  • rbtools.diffs.patcher
  • rbtools.diffs.tools
  • rbtools.diffs.tools.backends
  • rbtools.diffs.tools.backends.gnu
  • rbtools.diffs.tools.base
  • rbtools.diffs.tools.base.diff_file_result
  • rbtools.diffs.tools.base.diff_tool
  • rbtools.diffs.tools.errors
  • rbtools.diffs.tools.registry
  • rbtools.diffs.writers
  • rbtools.commands
  • rbtools.commands.main
  • rbtools.commands
  • rbtools.commands.base
  • rbtools.commands.base.commands
  • rbtools.commands.base.errors
  • rbtools.commands.base.options
  • rbtools.commands.base.output
  • rbtools.commands.alias
  • rbtools.commands.api_get
  • rbtools.commands.attach
  • rbtools.commands.clearcache
  • rbtools.commands.close
  • rbtools.commands.diff
  • rbtools.commands.info
  • rbtools.commands.install
  • rbtools.commands.land
  • rbtools.commands.list_repo_types
  • rbtools.commands.login
  • rbtools.commands.logout
  • rbtools.commands.patch
  • rbtools.commands.post
  • rbtools.commands.publish
  • rbtools.commands.review
  • rbtools.commands.setup_completion
  • rbtools.commands.setup_repo
  • rbtools.commands.stamp
  • rbtools.commands.status
  • rbtools.commands.status_update
  • rbtools.hooks
  • rbtools.hooks.common
  • rbtools.hooks.git
  • rbtools.testing
  • rbtools.testing.api
  • rbtools.testing.api.payloads
  • rbtools.testing.api.transport
  • rbtools.testing.commands
  • rbtools.testing.testcase
  • rbtools.testing.transport
  • rbtools.utils
  • rbtools.utils.aliases
  • rbtools.utils.browser
  • rbtools.utils.checks
  • rbtools.utils.commands
  • rbtools.utils.console
  • rbtools.utils.diffs
  • rbtools.utils.encoding
  • rbtools.utils.errors
  • rbtools.utils.filesystem
  • rbtools.utils.graphs
  • rbtools.utils.mimetypes
  • rbtools.utils.process
  • rbtools.utils.repository
  • rbtools.utils.review_request
  • rbtools.utils.source_tree
  • rbtools.utils.users
  • Glossary
  • General Index
  • Python Module Index
  • Release Notes
  • RBTools Documentation¶

    RBTools is a set of command line tools for working with Review Board and RBCommons. It’s there to help quickly get your code up for review, check on the status of changes, and eventually land your code in the codebase, amongst other uses.

    RBTools interfaces with your repository’s official command line tools, making it easy to generate suitable diffs or to apply changes across any supported type of repository without having to learn different sets of tools.

    Along with a variety of helpful commands, RBTools also provides a powerful Python client API for Review Board, giving you the flexibility to develop your own integrations.

    Let’s explore RBTools:

    • What’s in RBTools?

    • Getting started

    • Common RBTools workflows

    What’s in RBTools?¶

    The “rbt” Command¶

    All the RBTools commands are invoked through the rbt tool. This runs on Windows, Linux, and MacOS X, and contains a number of useful sub-commands through the following usage:

    $ rbt <command> [options] [<args>]
    

    You can get help on rbt or a sub-command in the following ways:

    $ rbt help
    $ rbt help <command>
    $ rbt <command> --help
    

    Some of the most commonly-used commands include:

    • post - Posts changes to Review Board

    • diff - Displays the diff that will be sent to Review Board

    • land - Lands a change in a local branch or on a review request

    • patch - Patches your tree with a change on a review request

    • setup-repo - Sets up RBTools to talk to your repository

    • status - Display the status of your outgoing review requests

    There’s a whole suite of additional commands that might also be useful:

    • alias - Create custom aliases for commands and operations

    • api-get - Retrieve structured information from the API

    • attach - Upload and attach files to a review request

    • clear-cache - Clear your local RBTools caches

    • close - Close a review request

    • install - Install special components for third-party integrations

    • list-repo-types - List all repository types supported by RBTools

    • login - Create a Review Board login session for RBTools

    • logout - Log RBTools out of Review Board

    • publish - Publish a review request

    • review - Create and publish reviews

    • setup-completion - Set up shell integration/auto-completion

    • stamp - Stamp a local commit with a review request URL

    • status-update - Register or update a “status update” on a review request, for automatic code review

    Learn more about RBTools commands.

    The RBTools Python API¶

    RBTools isn’t just a set of commands. It’s also a platform for writing your own code, including:

    • Custom rbt commands

    • Automation scripts for Review Board

    • Analytics tools

    • New automated code review integrations

    • Repository hooks and triggers

    And more.

    Using the RBTools Python API, you can write programs that talk to the Review Board API or to your local source code management system, all from Python.

    Learn more about the RBTools Python API.

    Getting Started¶

    We’ll walk you through getting RBTools ready to use with Review Board.

    1. Install RBTools.

      Steps are provided all major operating systems and Linux distributions.

    2. Authenticate with Review Board.

    3. Configure RBTools for your repositories.

      RBTools configuration lives in a .reviewboardrc file, which is usually stored in your source code repository, so everyone can share the same configuration.

      This is the first step to allow any of your developers to easily post changes using RBTools.

    4. Optionally, customize your RBTools experience:

      • Configure options and environment variables

      • Creating custom command aliases

      • Enable shell integration and auto-completion

      These can also live in a separate .reviewboardrc in your home directory, letting you make your RBTools experience your own.

    Common RBTools Workflows¶

    Every source code management system is different. We have guides on the most common workflows to help you get started:

    • Using RBTools With Cliosoft SOS

    • Using RBTools with Git

    • Using RBTools with HCL VersionVault and IBM ClearCase

    • Using RBTools With Perforce

    Keep up with the latest Review Board releases, security updates, and helpful information.

    About
    News
    Demo
    RBCommons Hosting
    Integrations
    Happy Users
    Support Options
    Documentation
    FAQ
    User Manual
    RBTools
    Administration Guide
    Power Pack
    Release Notes
    Downloads
    Review Board
    RBTools
    Djblets
    Power Pack
    Package Store
    PGP Signatures
    Contributing
    Bug Tracker
    Submit Patches
    Development Setup
    Wiki
    Follow Us
    Mailing Lists
    Reddit
    Twitter
    Mastodon
    Facebook
    YouTube

    Copyright © 2006-2025 Beanbag, Inc. All rights reserved.

    Terms of Service — Privacy Policy — AI Ethics Policy — Branding

    On this page

    • [Top]
    • What’s in RBTools?
      • The “rbt” Command
      • The RBTools Python API
    • Getting Started
    • Common RBTools Workflows