github.com/munnerz/test-infra@v0.0.0-20190108210205-ce3d181dc989/prow/cmd/gerrit/README.md (about)

     1  # Gerrit
     2  
     3  Gerrit is a Prow-gerrit adapter for handling CI on gerrit workflows. It can poll gerrit
     4  changes from multiple gerrit instances, and trigger presubmits on Prow upon new patchsets
     5  on Gerrit changes, and postsubmits when Gerrit changes are merged.
     6  
     7  ## Deployment Usage
     8  
     9  When deploy the gerrit component, you need to specify `--config-path` to your prow config, and optionally
    10  `--job-config-path` to your prowjob config if you have split them up.
    11  
    12  Set `--gerrit-projects` to the gerrit projects you want to poll against.
    13  
    14  Example:
    15  If you want prow to interact with gerrit project `foo` and `bar` on instance `gerrit-1.googlesource.com`
    16  and also project `baz` on instance `gerrit-2.googlesource.com`, then you can set:
    17  
    18  ```
    19  --gerrit-projects=gerrit-1.googlesource.com=foo,bar
    20  --gerrit-projects=gerrit-2.googlesource.com=baz
    21  ```
    22  
    23  `--cookiefile` allows you to specify a git https cookie file to interact with your gerrit instances, leave
    24  it empty for anonymous access to gerrit API.
    25  
    26  `--last-sync-fallback` should point to a persistent volume that saves your last poll to gerrit.
    27  
    28  ## Underlying infra
    29  
    30  Also take a look at [gerrit related packages](/prow/gerrit/README.md) for implementation details.
    31  
    32  You might also want to deploy [Crier](/prow/cmd/crier) which reports job results back to gerrit.