commit | 73fa5422a1dc087cf0d04eca109b6a2fd3be5419 | [log] [tgz] |
---|---|---|
author | Edwin Kempin <ekempin@google.com> | Wed Jul 01 14:06:51 2020 +0200 |
committer | Edwin Kempin <ekempin@google.com> | Wed Jul 01 14:07:30 2020 +0200 |
tree | c44a490e7b383e1b3a100b95496bed226cd0f1f5 | |
parent | 30961cc060680c50b6bde8acc693cfb3f530d22a [diff] |
Use 'example.com' domain for emails in tests 'test.com' is a real domain and shouldn't be used for email addresses in tests. 'example.com' is a domain reserved for use in documentation and tests, hence we should use this one. Signed-off-by: Edwin Kempin <ekempin@google.com> Change-Id: I18826a3995698ff18de9488c5bb76bd9464c4150
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/
(no need to pass it to --plugins flag)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