Google Git
Sign in
gerrit / plugins / checks / 942d26a424f1571b9f7411743bdbb85bc7f018bd
commit942d26a424f1571b9f7411743bdbb85bc7f018bd[log] [tgz]
authorJames E. Blair <jeblair@redhat.com>Thu Oct 24 13:41:32 2019 -0700
committerJames E. Blair <jeblair@redhat.com>Thu Oct 24 13:44:14 2019 -0700
tree50a4bdb0398791ac73e68aaffcf43435a978cd2e
parent5dae4c03d60cb53dc3b5b1165b1fe7a4beee7422 [diff]
Add .gitreview file

For folks used to using the git-review tool for interacting with
gerrit servers, it's necessary to have a .gitreview file in the
repo in question pointing to where the gerrit is.

Add one, pointing at gerrit-review.googlesource.com and listing that
https should be used. This will still require that someone add their
http authentication to the .gitcookies file, but otherwise should
work as expected.

A similar file was recently added to Gerrit itself.

Change-Id: I0f537704a41157e5deda16ae103145b896a3d34c
1 file changed
tree: 50a4bdb0398791ac73e68aaffcf43435a978cd2e
  1. gr-checks/
  2. java/
  3. javatests/
  4. proto/
  5. resources/
  6. test/
  7. .gitignore
  8. .gitreview
  9. bower.json
  10. BUILD
  11. LICENSE
  12. README.md
README.md

Gerrit Code Review Checks Plugin

This plugin provides a unified experience for checkers (CI systems, static analyzers, etc.) to integrate with Gerrit Code Review.

This plugin uses polymer-cli to test.

After bower install, running polymer test -l chrome will run all tests in Chrome, and running polymer serve and navigating to http://127.0.0.1:8081/components/checks/gr-checks/gr-checks-view_test.html allows for manual debugging.