commit | 3727cfd60d5aab06e1763872c500d8d31fb0fbb1 | [log] [tgz] |
---|---|---|
author | Damien Martin-Guillerez <dmarting@google.com> | Sun May 21 18:53:18 2017 -0700 |
committer | Damien Martin-Guillerez <dmarting@google.com> | Mon Jul 24 12:55:13 2017 +0200 |
tree | 7c8e519c4c2e5cdd2a986dd29bd19c6388cb9a35 | |
parent | bc3130aa3c2792b87172e9fe2da1027d7ef08018 [diff] |
Replace Bazel-Install by a pipeline job Simplifies the installation code by reducing the code specific to each platform and removing having 2 jobs for it. This new job stop installing HEAD Bazel which is no longer generated from the new pipeline. Change-Id: I2b03076cca22d1b0aeb0a3c60451abffe169d4f2
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.