commit | c2bf561f7596378eb29c29243b17fa98d7691aa1 | [log] [tgz] |
---|---|---|
author | Gal Paikin <paiking@google.com> | Tue May 26 11:50:01 2020 +0200 |
committer | Gal Paikin <paiking@google.com> | Tue May 26 11:50:01 2020 +0200 |
tree | dd9330d9f4e6793b0bac4adcc8fe08a23f6447dd | |
parent | 425c1d5c0e0bda13f5c13215fb4e7c54db281983 [diff] |
Add message-id to emails sent by the checks plugin Ib7068983d introduced the requirement to have a message-id for all emails that are sent through Gerrit. This change makes sure that checks plugin complies with this requirement. Change-Id: I791c5d549e1e09e7da507ae17a60a7f4101cbc81
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