commit | e96ce44075bef3362be8ea86987dd7b5ca2a1ad1 | [log] [tgz] |
---|---|---|
author | Damien Martin-Guillerez <dmarting@google.com> | Fri Jun 30 18:01:57 2017 +0600 |
committer | Damien Martin-Guillerez <dmarting@google.com> | Mon Jul 03 15:25:17 2017 +0600 |
tree | 8fdcc21e59317f1de9c18d09b4e8d7187098bbf8 | |
parent | 467e39bed62b2f3eeaee825d70704ae699e42ec2 [diff] |
Update CA certificate for the deploy image Or the slave ends up being in a inconsistent state at the beginng, failing to build bazel. Change-Id: I0691ec47c068b00f196264d317f318c9dc0aa285
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.