Reorganize jobs

Jobs are now grouped in folder by topic:

  - bazel contains the presubmit, and post-submit (splitted into nightly
  and release, reverting a86356a in the process). Fixes #94. The nightly
  build can be re-run on demand by the sheriff so no need to run it on
  every push.
  - maintenance contains pure maintenance jobs

Fixes #120.

Change-Id: I6ff44b6aa7003eedf5e50de7c5f5d090a2598a4d
11 files changed
tree: 742f2381ee09acb71e3fcef16fce38bebc742c98
  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.

For users of Bazel continuous integration system

If you are a user of the CI system, you might be interested in the following document:

  • owner: explains how to add a job for a repository owner.
  • user: explains how to use the CI system for a Bazel contributor.

For maintainers of Bazel continuous integration system

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