Google Git
Sign in
chromium / infra / gerrit-plugins / buildbucket / 43dff4679988579ee386379f401085c8d6756487
commit43dff4679988579ee386379f401085c8d6756487[log] [tgz]
authorEdward Lesmes <ehmaldonado@google.com>Thu Jul 09 04:07:14 2020
committerEdward Lesmes <ehmaldonado@chromium.org>Thu Jul 09 04:07:14 2020
treee98752ccf7870d674a2e7d70e8e522692c9cca8c
parent04e4c5ec6a80e341c03f1f65f4f5d2412e218a18 [diff]
buildbucket: Skip and log failures to list builders.

Listing builders for internal buckets fails with 404 for non-googlers,
so log failures and treat them as "no builders" response.

Bug: 1096190
Change-Id: I2e7b1831578d0aaad9812c26f1b62cef7b1578d2
Reviewed-on: https://chromium-review.googlesource.com/c/infra/gerrit-plugins/buildbucket/+/2288735
Reviewed-by: Josip Sokcevic <sokcevic@google.com>
2 files changed
tree: e98752ccf7870d674a2e7d70e8e522692c9cca8c
  1. src/
  2. test/
  3. .eslintrc.json
  4. .gitignore
  5. bower.json
  6. BUILD
  7. codereview.settings
  8. LICENSE
  9. package-lock.json
  10. package.json
  11. README.md
  12. run-with-prod-data.sh
  13. run-with-testsite.sh
  14. wct.conf.json
README.md

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 "luci.chromium.try"]
[bucket "luci.chrome.try"]

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.

If your project doesn't want the “retry failed” button to show, you can disable it:

[option]
  hide-retry-button = true

Development

To use with the local testsite

Use the script run-with-testsite.sh; this rebuilds the plugin with bazel, copies it over and restarts the local testsite. Example invocation:

GERRIT_DIR=~/gerrit GERRIT_TESTSITE_DIR=~/testsite ./run-with-testsite.sh

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_DIR=~/gerrit ./run-with-prod-data.sh

Testing

npm run wct-test

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