commit | e84c430eb75ad07f4c2136c3de7d86ea59fdb35a | [log] [tgz] |
---|---|---|
author | Damien Martin-Guillerez <dmarting@google.com> | Tue Aug 22 21:38:50 2017 +0200 |
committer | Damien Martin-Guillerez <dmarting@google.com> | Tue Aug 22 21:41:12 2017 +0200 |
tree | 4c149393d5f2dc4e497a89a4e400a267cde59dd8 | |
parent | 49f967c77e24acd993bec3fd6bf71ce1c8e8619c [diff] |
Fix the checked exception for a test failure The exception thrown was actually BazelUtils.BazelTestFailure. Also make sure all compilation of BazelTestFailure have the same version id for serialization so the exception thrown will be the same as the exception catched. Change-Id: I2682af2d4064cdfb6e930d651f37c92b36f52ce2
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.