| commit | b6ec5263e4e1ffeb6a4bd349927036c30918e110 | [log] [tgz] |
|---|---|---|
| author | Gavin Mak <gavinmak@google.com> | Tue Jul 13 22:20:07 2021 |
| committer | Gavin Mak <gavinmak@google.com> | Tue Jul 13 22:20:07 2021 |
| tree | 32e93175f0158a09a2e8ffceff71c21759b0c350 | |
| parent | 5cbac9d66bde5cf6e136e09ec6e2e0289f4dee4c [diff] |
Use window.buildbucket and update BUILD Bug: 1228935 Change-Id: I905eefb5278e4ec735959201781f719aba743c8d
The plugin queries the android-binary-size trybot for the current patchset on Gerrit, and gets the binary_size_plugin property. This property contains the metadata about the binary size metrics affected by the patchset in question. It then shows an inline table with the metric deltas + links to SuperSize output.
This plugin is configured via the chromium-binary-size.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 chromium-binary-size.config is below (this enables the plugin on the chromium/src repo using the android-binary-size trybot:
[host] gerrit = "chromium-review.googlesource.com" [repo "chromium/src"] builder = "android-binary-size" bucket = "try" project = "chromium"
All changes to chromium-binary-size.config files are instantly reflected. There is no caching period or need to restart the server.
git clone --recursive https://gerrit.googlesource.com/gerrit cd gerrit/plugins git clone https://chromium.googlesource.com/infra/gerrit-plugins/chromium-binary-size cd chromium-binary-size
Use the script run-with-prod-data.sh (based on polygerrit-ui/run-server.sh). You may change some paths by setting environment variables, for example:
GERRIT_DIR="$HOME/gerrit" ./run-with-prod-data.sh
npm run wct-test