Emergency fixes to the gerrit-verifier

- Don't use closure delegation strategy, instead refer directly
  to delegate.gerritBuild. Jenkins sandbox block invoking build when
  doing that, this is sad.
- Don't swallow build error, it is not useful as we do not propagate
  downstream errors.
- Don't use each with closure, jenkins bug again.
- Fix the access to gerritBuild so we don't set -1 even on success.

This fix is already up and running on ci.

Change-Id: If4eb61fca75d6f4a966787e370763624eb95cc80
2 files changed
tree: dad20977a61cbc47014ab9deebea6f9e9c5112d0
  1. base/
  2. docs/
  3. gce/
  4. gcr/
  5. gerrit-github-sync/
  6. jenkins/
  7. mac/
  8. templating/
  9. .gitignore
  10. AUTHORS
  11. CONTRIBUTING.md
  12. CONTRIBUTORS
  13. LICENSE.txt
  14. README.md
  15. WORKSPACE
README.md

Bazel continous integration setup

This workspace contains the setup for the continuous integration system of Bazel. This setup is based on docker images built by bazel.

Make sure you have a Bazel installed with a recent enough version of it. Also make sure gcloud and docker are correctly configured on your machine. Only docker version 1.10 or later is supported.

More documentation:

  • init.sh: initializes the whole CI platform. This may delete VMs and do other irreversible changes, so handle with care.
  • vm.sh: lets you control the machines (e.g. start/stop them, create/delete/reimage them), including the Jenkins controller and the executor nodes.
  • workflow: explains the CI workflow, and how you can test local changes with jenkins-staging
  • jobs: explains what jobs are running on the CI