Re-usable building blocks for Bazel build tool

Clone this repo:
  1. 5c26af9 Update Gerrit API to 3.2.0-rc0 and the snapshot API to 3.3.0-SNAPSHOT by David Pursehouse · 4 weeks ago master
  2. cd715d2 Merge branch 'stable-3.1' by Marco Miller · 8 weeks ago
  3. fc1bfdf Update Gerrit API to 3.1.4 by David Pursehouse · 9 weeks ago stable-3.1
  4. 5a21777 Merge branch 'stable-3.0' into stable-3.1 by David Pursehouse · 9 weeks ago
  5. 93641d3 Merge branch 'stable-2.16' into stable-3.0 by David Pursehouse · 9 weeks ago stable-3.0

Gerrit Code Review Rules for Bazel


These build rules are used for building Gerrit Code Review plugins with Bazel. Plugins are compiled as .jar files containing plugin code and dependencies.


To be able to use the Gerrit rules, you must provide bindings for the plugin API jars. The easiest way to do so is to add the following to your WORKSPACE file, which will give you default versions for Gerrit plugin API.

  name = "com_github_davido_bazlets",
  remote = "",
  commit = "2ede19cb2d2dd9d04bcb70ffc896439a27e5d50d",

Another option is to consume snapshot version of gerrit plugin API from local Maven repository (~/.m2). To use the snapshot version special method is provided:


Basic Example

Suppose you have the following directory structure for a simple plugin:


To build this plugin, your BUILD can look like this:

load("//tools/bzl:plugin.bzl", "gerrit_plugin")

    name = "reviewers",
    srcs = glob(["src/main/java/**/*.java"]),
    manifest_entries = [
        "Gerrit-PluginName: reviewers",
        "Gerrit-Module: com.googlesource.gerrit.plugins.reviewers.Module",
    resources = glob(["src/main/**/*"]),

Now, you can build the Gerrit plugin by running bazel build <plugin>.

For a real world example, see the reviewers plugin.


gerrit_plugin(name, srcs, resources, deps, manifest_entries):

Implicit output target

  • <name>.jar: library containing built plugin jar