commit | 5c2a2da0136666c0f9cb397629cf190bf9e51a81 | [log] [tgz] |
---|---|---|
author | Damien Martin-Guillerez <dmarting@google.com> | Tue Jul 04 17:13:44 2017 +0800 |
committer | Damien Martin-Guillerez <dmarting@google.com> | Tue Jul 11 21:24:30 2017 +0200 |
tree | f15649a791dbdd6553194f6951856cfbc7c48508 | |
parent | e8722a10e30809b9adf5ee4e0194c35952244df8 [diff] |
Test launcher: mount volumes in correct path The current path where the one from the docker server, not the container. I noticed the issue when I realized the resulting volumes was always empty. Change-Id: I52eb78bc21bec47cbb279db629efa349362de7fe
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.