Google Git
Sign in
gerrit / plugins / checks / d306a123fa9bf1b2b2cc66ce3bce5fa4f4ff6372
commitd306a123fa9bf1b2b2cc66ce3bce5fa4f4ff6372[log] [tgz]
authorTiago Quelhas <tjgq@google.com>Tue May 04 12:08:29 2021 -0700
committerTiago Quelhas <tjgq@google.com>Tue May 04 19:14:06 2021 +0000
tree3bfa4811800b76d4a00ae83875aec41aead0d782
parent8e731d1f597724db7c5d5dc43013341e6e31c981 [diff]
Add a dummy export statement to files imported as ES modules.

Inside Google, we are making it a requirement for files that are imported using ES syntax to be "marked" with an import or export statement.

Change-Id: I2c137f228bdd5aa72c8f6b3f8bf1c7a9d5579eb1
1 file changed
tree: 3bfa4811800b76d4a00ae83875aec41aead0d782
  1. gr-checks/
  2. java/
  3. javatests/
  4. proto/
  5. resources/
  6. test/
  7. .eslintrc.json
  8. .gitignore
  9. .gitreview
  10. bower.json
  11. BUILD
  12. LICENSE
  13. package-lock.json
  14. package.json
  15. README.md
README.md

Gerrit Code Review Checks Plugin

This plugin provides a unified experience for checkers (CI systems, static analyzers, etc.) to integrate with Gerrit Code Review.

When upgrading the plugin, please use init:

java -jar gerrit.war init -d site_path

More details about “init” in https://gerrit-review.googlesource.com/Documentation/pgm-init.html

UI tests

To run UI tests here will need install dependencies from both npm and bower.

npm run wct-test should take care both for you, read more in package.json.

You will need polymer-bridges which is a submodule you can clone from: https://gerrit-review.googlesource.com/admin/repos/polymer-bridges

Test plugin on Gerrit

  1. Build the bundle locally with: bazel build gr-checks:gr-checks
  2. Serve your generated ‘checks.js’ somewhere, you can put it under gerrit/plugins/checks/ folder and it will automatically served at http://localhost:8081/plugins_/checks/ (no need to pass it to --plugins flag)
  3. Use FE dev helper, https://gerrit.googlesource.com/gerrit-fe-dev-helper/, inject the local served ‘checks.js’ to the page

If your plugin is already enabled, then you can block it and then inject the compiled local verison.

See more about how to use dev helper extension to help you test here: https://gerrit.googlesource.com/gerrit-fe-dev-helper/+/master