Run the global presubmit on Presubmit-Ready+2

The change contains the following modification:
  - Use Presubmit-Ready instead of Verified for marking a change as ready
    to be tested. Verified will later be restricted to be set only by
    the CI system.
  - Add a parameter (CHANGE_NUMBER) to the global job and trigger a review
    of a change.
  - Extract the list of change Presubmit-Ready+2 and trigger the global pipeline
    for those changes.

Change-Id: I847bf79bc2898497e1e719c0a0eeb4a5e0d4eede
7 files changed
tree: 65d7a970cabcaae3177d7875b20d390577c77b4c
  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