Clone this repo:

Branches

  1. b25dac9 Revert "Add a subtle UI to estimate builder progress." by Aaron Gable · 3 days ago master
  2. d6c8c66 Buildbucket plugin: Check for Polymer inside Gerrit.install by Quinten Yearsley · 4 days ago
  3. ee28e1b Buildbucket plugin: Remove unused _isSignedIn by Quinten Yearsley · 6 days ago
  4. 3a1dd11 Fix buildbucket gerrit plugin to check for if Polymer is defined by Paladox none · 10 days ago
  5. 0e6bac1 Add a script to help with trying buildbucket plugin by Quinten Yearsley · 12 days ago

Buildbucket Plugin for Gerrit

Usage

This plugin is configured via the buildbucket.config file present in the repo‘s refs/meta/config ref, as well as the same file in all repositories in the repo’s inheritance chain (up to and including All-Projects).

An example buildbucket.config is below:

[host]
  git = "chromium.googlesource.com"
  gerrit = "chromium-review.googlesource.com"

[bucket "chromium.buildbucket.swarming"]
  builder = infra_presubmit
  builder = infra_linux64
  builder = infra_mac
  builder = infra_win
[bucket "tryserver.infra"]
  builder = Infra Presubmit
  builder = Infra Linux Trusty 64 Tester
  builder = Infra Linux Precise 32 Tester
  builder = Infra Mac Tester
  builder = Infra Win Tester

In the vast majority of cases, the host.git and host.gerrit values are global to the entire host, so that stanza is specified in the All-Projects repo. Buckets and builders, on the other hand, are almost always very repository-specific, and so are only specified in “leaf” repositories which are not in any other repo's inheritance chain.

All changes to buildbucket.config files are instantly reflected. There is no caching period or need to restart the server.

Development

To use with the local testsite

ln -s /path/to/buildbucket-plugin plugins/buildbucket
bazel build plugins/buildbucket && \
  rm -rf ../gerrit_testsite/plugins/buildbucket.jar && \
  cp bazel-genfiles/plugins/buildbucket/buildbucket.jar ../gerrit_testsite/plugins/ && \
  ../gerrit_testsite/bin/gerrit.sh restart

To use with the polygerrit-ui server against live data

Use the script run-with-prod-data.sh; this creates a temporary directory with the plugin source in the expected layout and then invokes polygerrit-ui/run-server.sh. Example invocation:

GERRIT=~/gerrit ./run-with-prod-data.sh

Testing

# Install dependencies.
npm install -g bower
npm install -g web-component-tester
cd test/
bower install

# Run the tests from the directory root.
cd ../
wct

Note: Testing is disabled for Safari due to this issue.