commit | f4af155565dfc5baee0e51cc12dd4fab9d667ee6 | [log] [tgz] |
---|---|---|
author | Damien Martin-Guillerez <dmarting@google.com> | Fri Aug 25 12:38:53 2017 +0200 |
committer | Damien Martin-guillerez <dmarting@google.com> | Fri Aug 25 12:24:12 2017 +0000 |
tree | a8ca1af216386e446bb86e8878c241361bfd3ae3 | |
parent | 3b8c3b28d70917e2046d36e78c1a120546de6cd1 [diff] |
Fix the path to the install-bazel job Change-Id: Iedd63dcd62010b6ccdd48a059350db640783d056
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.