commit | 84ce93db82377b8235b3a2822eda9606b3a39788 | [log] [tgz] |
---|---|---|
author | Damien Martin-Guillerez <dmarting@google.com> | Fri Sep 01 14:45:40 2017 +0200 |
committer | Damien Martin-guillerez <dmarting@google.com> | Fri Sep 01 15:09:52 2017 +0000 |
tree | 1aa920419140cfc0a044adad31f945fadb443640 | |
parent | 0db9b06b16e5e6d4d18efa4c5cd5fe70335ca9ba [diff] |
Archive the build event files in all the case Previously a build failure would have had the result of losing the build event files since we were archiving them only on test failure. This change will also stop creating empty event files when there are none. Change-Id: Ic64f406574804f0d90afe87c951475d976dc5949
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.