commit | 698df7513f3bdd4751487a8a81311b85fdae6891 | [log] [tgz] |
---|---|---|
author | Dmitrii Filippov <dmfilippov@google.com> | Tue Feb 14 11:44:24 2023 +0100 |
committer | Dmitrii Filippov <dmfilippov@google.com> | Tue Feb 14 11:44:54 2023 +0100 |
tree | 7f94c3a3ffcce01b0f10a83c7d5938d0af7f137f | |
parent | 6338472bce64c9dc085f97d276ea725a311a6f87 [diff] |
Wrap ref updates in the correct RefUpdateContext. Bug: Google b/261005032 Release-Notes: skip Forward-Compatible: checked Change-Id: If48c444ad172038896f43076ea8f1e03cf32afa1
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
.