commit | cba6eb3d7fb7ba2af432aa890d736cded65ef47b | [log] [tgz] |
---|---|---|
author | Damien Martin-Guillerez <dmarting@google.com> | Wed Jul 12 17:14:20 2017 +0200 |
committer | Damien Martin-Guillerez <dmarting@google.com> | Sat Jul 15 11:10:38 2017 +0200 |
tree | ae094b41fe4db5fec3d373696cbd955e7bf91c35 | |
parent | efe871fea5c7404f66040d5600d1059b10f9f34c [diff] |
Generate a build log to push to GCS with the release To do so, save the log from the Jenkins master, stop saving the README.md file. Moved the pushing release to a specific steps so it can actually access those special JenkinsUtils functions. Change-Id: I6ef891d302270c59efbf038dfac0ab364f134833
This workspace contains the setup for the continuous integration system of Bazel. This setup is based on docker images built by bazel.
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.