commit | b349da477cf472e55184f6d24f96a6c8279fc6c0 | [log] [tgz] |
---|---|---|
author | Ben Rohlfs <brohlfs@google.com> | Tue Apr 27 13:51:06 2021 +0200 |
committer | Ben Rohlfs <brohlfs@google.com> | Wed Apr 28 11:37:15 2021 +0200 |
tree | 768ade1e171a72439f3c27efbd6c369fa6d5f238 | |
parent | 09c93af05a72cc83097c1be6ec6062d36f59a5a5 [diff] |
Remove old obsolete Checks UI Keep the dialog for checker configuration. Will add this as a top-level action to the new Checks UI. Change-Id: If77cb2615ba9a0838a39f478aa225df8f608a074
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