commit | 9702d6e37f7d582e98be4486c49f4442adf268be | [log] [tgz] |
---|---|---|
author | Ben Rohlfs <brohlfs@google.com> | Thu Jul 01 09:41:28 2021 +0200 |
committer | Ben Rohlfs <brohlfs@google.com> | Thu Jul 01 09:50:32 2021 +0200 |
tree | 2b0b27b9aaa9ad679f75a025747faad938941055 | |
parent | 24372de7e21844ab64c54d7c42ee9b7905477866 [diff] |
Add a "rerun" action also for running checks Bug: Issue 14724 Change-Id: I6ad2d6559b26a76924cb0219fb11747bf4cc74c2
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