commit | ba0f8094574bb568ce4abb00d058bbdee21512d6 | [log] [tgz] |
---|---|---|
author | Damien Martin-Guillerez <dmarting@google.com> | Mon Aug 21 11:46:01 2017 +0200 |
committer | Damien Martin-Guillerez <dmarting@google.com> | Mon Aug 21 13:14:25 2017 +0200 |
tree | 82823ba9e5621cae4b95ef7159b778070b50efa3 | |
parent | 382e19231dab9a7ed10a9b69d83736ab122c07e6 [diff] |
Revert "Mark individual step as failure" This reverts commit 272a2bf76f0e00c5066aa6a05354d13ce5968727. This commit mark every build red when there is only test failures. It reduces the information and make the downstream projects harder to analyze. To double down, it does not work, the whole build is marked as broken but we cannot locate the failing step: http://ci.bazel.io/blue/organizations/jenkins/Global%2Fbazel-tests/detail/bazel-tests/180/pipeline Change-Id: Ic2aa30360d5d7e7dada7198f3aa9cc073f1a1906
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.