commit | 8e731d1f597724db7c5d5dc43013341e6e31c981 | [log] [tgz] |
---|---|---|
author | Ben Rohlfs <brohlfs@google.com> | Thu Apr 29 15:34:20 2021 +0200 |
committer | Ben Rohlfs <brohlfs@google.com> | Thu Apr 29 15:34:20 2021 +0200 |
tree | 2320ff0bb77d9fbf4a0b3b95851d11f0c2eb8849 | |
parent | cd4e024ddca7ffc7d97cef6a4186b24b0163b63c [diff] |
Adapt the Checks plugins to change of the action response See change 304482 Change-Id: I02d05e62153566de983abec82959b9853bc97487
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
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
bazel build gr-checks:gr-checks
gerrit/plugins/checks/
folder and it will automatically served at http://localhost:8081/plugins_/checks/
(no need to pass it to --plugins flag)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