commit | c8d59f65eb9bd6ddc8b895a35c4f17789d562a2f | [log] [tgz] |
---|---|---|
author | Edwin Kempin <ekempin@google.com> | Fri Feb 02 11:54:22 2024 +0000 |
committer | Edwin Kempin <ekempin@google.com> | Fri Feb 02 12:00:41 2024 +0000 |
tree | 03e2874428209aa96fe8401d7922627e911bf3fd | |
parent | 7885af5756ae817bf3fc5d0ed140d8de6148251a [diff] |
Use assertThat from Truth instead of Truth8 The Truth team moved methods from Truth8 into Truth. Change-Id: I9eef394fd3eb4fb9d5430c0be6df1df69cf8b2a5 Signed-off-by: Edwin Kempin <ekempin@google.com>
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
.