Add downstream jobs for the global pipeline

Almost #55

This change does test downstream test with the good refs
so will test release branch itself, so when rolled-out it
will fix also #59.

Roll-out plan:
  - Set that on ci.bazel.io, test it manually.
  - Create a test release and trigger the pipeline manually with it
  - Replace Github PR and Gerrit CR with pipelien job, test them
  - Set the github trigger to trigger that job instead of the legacy pipeline
  - Delete the legacy pipeline
  - Replace the legacy jobs with the new shiny jobs.

Change-Id: Icbaf9344407838302bab8db4b80c7b08ecd11c25
6 files changed
tree: cebd239b3c300b93a32e9088a66570e8159a8dd0
  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