commit | 73f20d9db6b07227471c1a00d3b6ac7141e9eafa | [log] [tgz] |
---|---|---|
author | Damien Martin-Guillerez <dmarting@google.com> | Wed Apr 19 00:54:38 2017 +0200 |
committer | Damien Martin-Guillerez <dmarting@google.com> | Tue May 23 07:55:16 2017 -0700 |
tree | fd58b5a875fa3589203f7f322bd9266616a74187 | |
parent | 78f809f82e152e37e3777b71e422d0b1d0fd0ea9 [diff] |
Add a bazelJob pipeline step This step execute bazel and will be used for running all the job on CI using Jenkins pipeline. This was tested on a local instance of ci, using a linux slave. It mimick the way we are currently doing bazel testing, and should work allright on Windows but was not fully tested yet. Change-Id: If93663a3d7e9f2589fef8ec78df8330e8c3acc2f
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.