Change from placeholder .html to .js module .html is automatically generated by google3's build rules to make the migration of js separate from the java migration (because gerrit java code is released on a different schedule than js). Now that the js changes have landed, switch java to load the js file directly. Change-Id: I809b0f2dc6fcdd716672730a0415b306de5193ea
1 file changed
tree: 9ce96da3610458c204c5cd36d17d45f82883c599
  1. java/
  2. static/
  3. test/
  4. .eslintrc.json
  5. .gitignore
  6. bower.json
  7. BUILD
  8. codereview.settings
  9. LICENSE
  10. package-lock.json
  11. package.json
  12. README.md
  13. run-with-prod-data.sh
  14. run-with-testsite.sh
  15. wct.conf.json
README.md

Chromium Binary Size Plugin for Gerrit

How it works

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.

Usage

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.

Development

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 

Run the polygerrit-ui server against live data

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 

Testing

# Install dependencies. npm install -g bower npm install -g web-component-tester bower install wct