commit | 737bb53203f88abc0fede51be52ff1d2a6392e53 | [log] [tgz] |
---|---|---|
author | Tao Zhou <taoalpha@google.com> | Fri Apr 17 17:24:05 2020 +0200 |
committer | Tao Zhou <taoalpha@google.com> | Tue Apr 21 09:54:04 2020 +0000 |
tree | fbced5679d665026417d2e8ed2222ae16cc521ba | |
parent | 8e5524b99e45eabe22bc5abb291afce42d64c01c [diff] |
Migrate checks plugin to polymer 3 Support run tests without depending on Gerrit. But still need polymer-bridges to maker polymer available. Change-Id: I3062b8d2b8f3a8c7b9227b76fb8d2f2793342144
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