commit | e72bced948ea85dbf737afb1fc22494f1aa25d04 | [log] [tgz] |
---|---|---|
author | Edwin Kempin <ekempin@google.com> | Mon Dec 21 15:25:57 2020 +0100 |
committer | Edwin Kempin <ekempin@google.com> | Mon Dec 21 15:30:15 2020 +0100 |
tree | 73657e4e928ce49840944fd57bdbda85b0269ae4 | |
parent | ab49a63f5c159bda42d9ad1bdb9286bede6c5de4 [diff] |
Drop tests for creating changes on checker refs Since change If5fb50e1f the Create Change REST endpoint no longer allows to create changes on NoteDb refs. Drop the tests as this is non-critical functionality for the checks plugin and also the checks plugin is discontinued. Signed-off-by: Edwin Kempin <ekempin@google.com> Change-Id: I6d7ee35e9a94cd7a4584d5fe764d50408e19eb73
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