commit | 405a0be281f39311d16c4c3adfb7c34d9192bb91 | [log] [tgz] |
---|---|---|
author | Damien Martin-Guillerez <dmarting@google.com> | Fri May 19 18:11:20 2017 -0400 |
committer | Damien Martin-Guillerez <dmarting@google.com> | Wed May 24 19:56:23 2017 -0700 |
tree | f0b1a5eaac52f96fe36b349489f427ac8c888c6b | |
parent | f23cabaf730f91ea9761335f0bb3ab12d6f3edf8 [diff] |
Add configuration files for each job default.json will be used for a job without a specific json configuration file. Ideally those configuration file would live next to the repository they are used to describe the tests we need to run for the repository. Change-Id: I4fa2d31836ddd70f23b08a717e3cb881b5a8d9d1
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.