| commit | 0294de9b3428ec78fe72d183cfa04e421d45e886 | [log] [tgz] |
|---|---|---|
| author | Damien Martin-Guillerez <dmarting@google.com> | Tue Jul 25 23:59:40 2017 +0200 |
| committer | Damien Martin-guillerez <dmarting@google.com> | Wed Jul 26 10:00:58 2017 +0000 |
| tree | 264b39d948b3b9585eb7502c3e66dd6e12cd9b01 | |
| parent | 3e61958fcab81089036c02b4005ee4b9f2469e68 [diff] |
Add the executable flag to the Bazel binary for custom Bazel On FreeBSD the flag was missing leading to permission denied. Fixes #104. Change-Id: Ie9bd9caaba9a451630e3b451b58d8242480187ab
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.