Google Git
Sign in
gerrit / plugins / checks / 59256c0de2ec082f457550e69da37514a56cfdca
commit59256c0de2ec082f457550e69da37514a56cfdca[log] [tgz]
authorBen Rohlfs <brohlfs@google.com>Thu Feb 25 11:04:20 2021 +0100
committerBen Rohlfs <brohlfs@google.com>Thu Feb 25 11:06:46 2021 +0100
treeb1f5e1aab67db1d27fe4007711f00cc2c7ed464d
parent648881efe1ef5cb0be5f6f7e2f01439ae7c02b0e [diff]
Add some more data when converting checks for the new UI

If the check has no message, then use a generic message with a duration
string.

Also fix the error handling when triggering a run.

Bug: Issue 14141
Change-Id: Ie17347540c7e343d69201c4d90a2bce57bbec5f5
1 file changed
tree: b1f5e1aab67db1d27fe4007711f00cc2c7ed464d
  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