commit | 2e3f9f291310b4f3822b4900c72a4e781d37c2bf | [log] [tgz] |
---|---|---|
author | Gal Paikin <paiking@google.com> | Thu Dec 16 12:27:34 2021 +0100 |
committer | Gal Paikin <paiking@google.com> | Thu Dec 16 12:27:34 2021 +0100 |
tree | 91fa47d92453d9463240756ff8fa7008bd8c9e42 | |
parent | 00c52fca7cfbfecc5facc71e022ddaed3d1098e9 [diff] |
Fix calls to logger's log(string) This is in preparation for Google's PII efforts that are planned later. Google-Bug-Id: b/209582622 Change-Id: Ia779d4bcc0a6d2238908f164c3befc89a157bf52
The Gerrit team at Google has decided to discontinue work on the checks plugin. The recommended solution is [https://gerrit-review.googlesource.com/Documentation/pg-plugin-checks-api.html](Checks UI) which surfaces results from an external CI/analysis system.
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 enable sending email notifications for “checks” status updates, you'll need to create the email templates in <your-site-path>/etc/mail
. In the simplest form, simply rename the example templates:
cd "<your-site-path>" mv etc/mail/CombinedCheckStateUpdated.soy{.example,} mv etc/mail/CombinedCheckStateUpdatedHtml.soy{.example,}
For running unit tests execute:
bazel test --test_output=all //plugins/checks/web:karma_test
For checking or fixing eslint formatter problems run:
bazel test //plugins/checks/web:lint_test bazel run //plugins/checks/web:lint_bin -- --fix "$(pwd)/plugins/checks/web"
For testing the plugin with Gerrit FE Dev Helper build the JavaScript bundle and copy it to the plugins/
folder:
bazel build //plugins/checks/web:checks cp -f bazel-bin/plugins/checks/web/checks.js plugins/
and let the Dev Helper redirect from .+/plugins/checks/static/checks.js
to http://localhost:8081/plugins_/checks.js
.