commit | 0eaffba8775f95cccac487ad0e635a2801416b91 | [log] [tgz] |
---|---|---|
author | Ben Rohlfs <brohlfs@google.com> | Wed Jan 27 12:20:55 2021 +0100 |
committer | Ben Rohlfs <brohlfs@google.com> | Wed Jan 27 12:20:55 2021 +0100 |
tree | 88228b76a116d0d2393d863cfa994f6be0f3bf71 | |
parent | fba782d915b88502888e20a856d47351901d4e2a [diff] |
Add a 'run' action to reboot checks plugin Change-Id: I6914da5a34bb687d999f6dda8faeb4e4ddf5d401
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