| commit | c948aead3bfae0e15dce683ac23d42fb5d2b1d69 | [log] [tgz] |
|---|---|---|
| author | Patrick Hiesel <hiesel@google.com> | Tue Mar 01 08:55:53 2022 +0100 |
| committer | Patrick Hiesel <hiesel@google.com> | Tue Mar 01 08:56:20 2022 +0100 |
| tree | 6cf5441d86e2f14ca0f18ae3ccc14bf23fa40008 | |
| parent | e7991abd4b56de964c10f43132ed4154069353aa [diff] |
Remove unnecessary leading dot from template names and template calls Change-Id: Id208cafd880a5d2e711a4da20c40d50dc77f011b
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.