commit | cd4e024ddca7ffc7d97cef6a4186b24b0163b63c | [log] [tgz] |
---|---|---|
author | Ben Rohlfs <brohlfs@google.com> | Tue Apr 27 15:18:39 2021 +0200 |
committer | Ben Rohlfs <brohlfs@google.com> | Wed Apr 28 13:37:49 2021 +0200 |
tree | 434ac412a64759c4a01fb23b95fa1ba01f607da5 | |
parent | b0144b5fd625834860efe949614fc27044ff2f84 [diff] |
Add a popup for configuring checks as a top-level action Bug: Issue 14336 Change-Id: I09ac406277f1f78c76b6263c9f4f86bb68445c4f
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