commit | cb662632d8deeeac0839366461889f060435f5d0 | [log] [tgz] |
---|---|---|
author | Damien Martin-Guillerez <dmarting@google.com> | Mon Aug 21 15:18:11 2017 +0200 |
committer | Damien Martin-Guillerez <dmarting@google.com> | Mon Aug 21 17:57:18 2017 +0200 |
tree | 22079fa3a1f0cb9710154c1184585e55fe3e2fdd | |
parent | 57136a1a65b50c5e6af1e42d558b7011994a9ed5 [diff] |
Use checked exception to signal a test failure Instead of errors or messaging + UNSTABLE. This enable to mark the step as error but the build as unstable, distinguishing between different failures. Change-Id: Ib4da32af3b09b80825c1f35dae571c1150a52d44
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.