commit | de9da1dfbd9661badeeb8ecf8c34215c032a393c | [log] [tgz] |
---|---|---|
author | Ben Rohlfs <brohlfs@google.com> | Tue Feb 09 15:44:56 2021 +0100 |
committer | Ben Rohlfs <brohlfs@google.com> | Tue Feb 09 15:44:56 2021 +0100 |
tree | ff7fa087a7d1760a53a25eeca4f300d9d11a21b6 | |
parent | 0eaffba8775f95cccac487ad0e635a2801416b91 [diff] |
Use a different flag for enabling the new Checks UI The experimental flag has been broken up into one for Gerrit, one for buildbucket and one for the old Checks plugin. Change-Id: I324b34b5f7b1708ae800095f0e6c43fd45f94f61
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