commit | 2e641833d5667f8b62610169cc649746b7dfa57e | [log] [tgz] |
---|---|---|
author | Damien Martin-Guillerez <dmarting@google.com> | Thu Jul 27 13:03:50 2017 +0200 |
committer | Damien Martin-Guillerez <dmarting@google.com> | Thu Jul 27 13:03:50 2017 +0200 |
tree | 3e9d64c42b97910d0cfb164c76a6ec872cea43c1 | |
parent | f008017ea5a186426679d295eca1c11563f19d14 [diff] |
Cosmetic changes to Bazel config files after moving them to the Bazel repo. Change-Id: Ia1147e2c1132932d7905863774ff91bfd90c49ce
This workspace contains the setup for the continuous integration system of Bazel. This setup is based on docker images built by bazel.
If you are a user of the CI system, you might be interested in the following document:
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.