commit | 272a2bf76f0e00c5066aa6a05354d13ce5968727 | [log] [tgz] |
---|---|---|
author | Klaus Aehlig <aehlig@google.com> | Thu Aug 10 18:23:50 2017 +0200 |
committer | Klaus Aehlig <aehlig@google.com> | Thu Aug 10 18:23:50 2017 +0200 |
tree | ff29424ef7fa38a26a1bbfddd8bff25160108d71 | |
parent | 53658b6f475f362da2d0e34f8cfc1fd876c32921 [diff] |
Mark individual step as failure When investigating a problem it is usually more important to know which individual step failed, than knowing the difference between "tests failing" and "failed to build". Therefore use Jenkins "error" command instead of marking the whole pipeline as "UNSTABLE". Change-Id: Ia14be4e8c76062e142523f6d01417b0f6522036f
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.