commit | f008017ea5a186426679d295eca1c11563f19d14 | [log] [tgz] |
---|---|---|
author | Klaus Aehlig <aehlig@google.com> | Wed Jul 26 12:56:10 2017 +0200 |
committer | Klaus Aehlig <aehlig@google.com> | Wed Jul 26 14:29:08 2017 +0200 |
tree | c6b69e3b169ba560622a41f349e6a55975714cad | |
parent | f06959b27c0a0ebe6ea7731e9c7022b3f6658d7a [diff] |
For FreeBSD, fix #!-lines ...also for bootstrapping, so that we can also run tests with bazel from head. Change-Id: If180cd7f4003a32b236af28b0888e3f51b150776
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.