commit | e5cc92c4330942ac22b863ce7c76036842e1a928 | [log] [tgz] |
---|---|---|
author | David Pursehouse <dpursehouse@digital.ai> | Thu Jun 11 16:40:35 2020 +0900 |
committer | David Pursehouse <dpursehouse@digital.ai> | Thu Jun 11 16:40:35 2020 +0900 |
tree | 3dc2395ef86c7ab4018db57fd5eec64f198971ca | |
parent | 07d6997fc967e0f1719a012964075edc3a55d7b5 [diff] | |
parent | 50848a3e3af7fe457013bc5f2fdec0b1b519d535 [diff] |
Merge branch 'stable-3.2' * stable-3.2: CheckerRefMigration: Use AllProjectsNameOnInitProvider Docs: remove stray single-qoute Change-Id: I46633b8d12051b3ccc091dd829c67449a4c8461c
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