I have updated the wiki to describe how to use Jenkins. I am copying my changes below.
If you see something that could use touching up, you can edit the page at https://cwiki.apache.org/confluence/display/IMPALA/Using+Gerrit+to+submit+and+review+patches ++++++++++++++++++++++++++++++++++++++++++++++ Verifying and submitting a patch (Impala committers only!) Once a change has a +2 from a committer and no -1 from any committer, it is ready to be verified and merged to gerrit. Remember that the source of truth for what is in Impala is the official Apache git server. Gerrit serves as a staging ground for reviewing patches, and once a patch is approved, a sort of waiting room while patches wait for a committer to officially move them to the Apache git repo. To verify a patch, we use one of two different automated processes. Both are restricted to use by committers. If you are not a committer and your patch has been +2ed, please ask a committer to run the verification for you. First, log in to http://jenkins.impala.io:8080. If you are a committer and forgot your password, ask [email protected] for help. Someone will reset your password. Then, if your commit changes only files in the docs/ folder: 1. Go to http://jenkins.impala.io:8080/job/gerrit-docs-submit/build?delay=0sec. Put your gerrit patch URL in the PATCH_URL field. Leave the other fields with their default values. Press "Build". 2. If all goes well, you will see messages like "Build started: http://jenkins.impala.io:8080/job/gerrit-docs-submit/4/"; and "Verified+1" and "Change has been successfully cherry-picked as 84ee40428dbb18146760adec8c5a03559f527ddb by Impala Public Jenkins" on your patch. 3. If something breaks, go to the URL Jenkins posted to your patch. It will look something like this: http://jenkins.impala.io:8080/job/gerrit-docs-submit/10/. Click on the "Build Artifact" and "Console Output" to look at the logs and figure out what went wrong. If your commit doesn't change any files in the docs/ folder: 1. Go to http://jenkins.impala.io:8080/job/gerrit-verify-dryrun/build?delay=0sec. Put your gerrit patch URL in the PATCH_URL field. Leave the other fields with their default values. Press "Build". 2. If all goes well, you will see messages like "Build started: http://jenkins.impala.io:8080/job/gerrit-verify-dryrun/151/"; and "Verified+1" and "Change has been successfully cherry-picked as 84ee40428dbb18146760adec8c5a03559f527ddb by Impala Public Jenkins" on your patch. 3. If something breaks, go to the URL Jenkins posted to your patch. It will look something like this: http://jenkins.impala.io:8080/view/Gerrit/job/gerrit-verify-dryrun/141/. Click on the "Build Artifact" and "Console Output" to look at the logs and figure out what went wrong. If your commit touches files both in and out of the docs/ folder, run http://jenkins.impala.io:8080/job/gerrit-verify-dryrun/build?delay=0sec first, following the directions above. Once it succeeds, run http://jenkins.impala.io:8080/job/gerrit-docs-submit/build?delay=0sec.
