commit | 0c7ea0a81b2200f4eb25228fa23d2a7953248ff3 | [log] [tgz] |
---|---|---|
author | David Ostrovsky <david@ostrovsky.org> | Tue Apr 21 23:57:30 2020 +0200 |
committer | David Ostrovsky <david@ostrovsky.org> | Tue Apr 21 23:57:30 2020 +0200 |
tree | 8ea4f6e98c35c8a05fcb850a8a573423158c176e | |
parent | 737bb53203f88abc0fede51be52ff1d2a6392e53 [diff] |
Fix loading of checks plugin In I3062b8d2b8f the plugin was migrated to use Polymer 3. As the consequence, the plugin artifact was changed from checks.html and checks.js to checks.js only. However, the name of entry point wasn't adapted, so that the plugin cannot be loaded. Change-Id: I673c599567f6b24d8c41873ae25e010e6ac75fc1
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/
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