|author||Gavin Mak <firstname.lastname@example.org>||Wed May 12 22:44:51 2021|
|committer||Gavin Mak <email@example.com>||Wed May 12 22:44:51 2021|
Remove dead code referencing non-unexpected results Bug: 1174869 Change-Id: I2ccc5027d931e1cc27a132f8ec93ed0cbc9e55df Reviewed-on: https://chromium-review.googlesource.com/c/infra/gerrit-plugins/buildbucket/+/2891598 Reviewed-by: Nodir Turakulov <firstname.lastname@example.org>
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.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
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
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:
npm run wct-test
Note: Testing is disabled for Safari due to this issue.