Google Git
Sign in
gerrit / plugins / checks / ffaeb8cc66436e0afddc6d4ae2bfc26f8e66bcd1
commitffaeb8cc66436e0afddc6d4ae2bfc26f8e66bcd1[log] [tgz]
authorGal Paikin <paiking@google.com>Thu Sep 24 11:16:32 2020 +0300
committerGal Paikin <paiking@google.com>Thu Sep 24 12:46:11 2020 +0300
treef664b8362f6318d6541830294a5bbf844135112f
parentf508353fc5f93d35d07279857aba5d9cf38de658 [diff]
Adjust email tests to have new footers

Added upstream in I70119346.
The footers are removed from the tests completely so that the tests
don't break every time the footers are changed upstream (those footers
are not related to those tests).

Change-Id: Ie9b79154dd6f99e57136a1a5ffb35369e033cf24
1 file changed
tree: f664b8362f6318d6541830294a5bbf844135112f
  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