commit | e2e2793863409932d90214f3ba818e8698767314 | [log] [tgz] |
---|---|---|
author | Damien Martin-Guillerez <dmarting@google.com> | Fri May 05 13:13:29 2017 +0200 |
committer | Damien Martin-Guillerez <dmarting@google.com> | Fri May 05 13:23:02 2017 +0200 |
tree | 702c9c3fccb5fc6998971552e482c7e4832a9860 | |
parent | 36f257aaeec23519325b85b6ea615638a3b0231e [diff] |
Add bazel clean for JDK7 as workaround of bazelbuild/bazel#2941 This is a temporary workaround to avoid random failures of JDK7 builds until 0.5.0 is released. Change-Id: I1323c128978190274f65018f32fd6b9afe8e681f
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 master and the Jenkins slaves