commit | b6ec5192b9cdb70e16e5ea557a9b03e696d93685 | [log] [tgz] |
---|---|---|
author | Damien Martin-Guillerez <dmarting@google.com> | Fri Aug 25 13:27:18 2017 +0200 |
committer | Damien Martin-guillerez <dmarting@google.com> | Fri Aug 25 11:49:59 2017 +0000 |
tree | 0077ca16bce8092c376ba711c7b1811f4a62747a | |
parent | 154aa1a6a8aa02814ffd34d9766f3f0c2c09f880 [diff] |
Double the number of docker executioner Even though they are rarely used, bazel-docker-tests is really slow so double the number of executioner that can run it so we can shard it. Issue #98. Change-Id: Ib98c9850ac9ec3a4815d59c403b7921eeded0e0e
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.