|author||Oleh Prypin <email@example.com>||Mon May 28 06:00:01 2018|
|committer||Oleh Prypin <firstname.lastname@example.org>||Mon May 28 06:00:01 2018|
Rearrange files to make the plugin more easily testable Change-Id: Ic71f872667cf87128f0712b75b8db3d19ec85715
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.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.
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:
# 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.