| commit | e31aa07656b59f2fd4cad813c0d0eabd522f10e7 | [log] [tgz] |
|---|---|---|
| author | Damien Martin-Guillerez <dmarting@google.com> | Mon Sep 04 14:27:16 2017 +0200 |
| committer | Damien Martin-Guillerez <dmarting@google.com> | Mon Sep 04 14:44:59 2017 +0200 |
| tree | b7a8d7b310e1688154c07959ef014011196f6f9f | |
| parent | c7dfd807a74f38a596f9ae7f0ffd421045b45741 [diff] |
Adds the ability to specify startup options So we can inject --host_jvm_args=-Dbazel.DigestFunction=... to test remote caching/execution. Change-Id: I2cf3500c4d98f42c4112a4a9c66c85e2bfdd2f6a
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.