| commit | 33dd9cccaa83b40ee8f5d4677ba994e4d446528e | [log] [tgz] |
|---|---|---|
| author | Gavin Mak <gavinmak@google.com> | Fri Jul 16 18:21:00 2021 |
| committer | Gavin Mak <gavinmak@google.com> | Thu Aug 12 20:39:51 2021 |
| tree | bdaa8106e2d5d88bfb2a5ae04e42970f230bac15 | |
| parent | 0ae2ecb8a71c85ed77ce139c5a7e562353c9a5d8 [diff] |
Use Checks to display chromium-binary-size-table-view Currently, the plugin only displays information in a cell format. This change displays this same information using a new table under the Checks tab. Both formats are still available. Bug: 1228935 Change-Id: Icaa809874a5ff1db9539a868577494425fcfde64
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