commit | 995e0a394b71da51df2e2d82eef59e9a51bef4d3 | [log] [tgz] |
---|---|---|
author | Damien Martin-Guillerez <dmarting@google.com> | Mon May 29 00:44:02 2017 -0700 |
committer | Damien Martin-Guillerez <dmarting@google.com> | Mon Jul 03 16:42:05 2017 +0600 |
tree | 02102bf3a7d7ef2254445e3594c1c09af9aeabfc | |
parent | 818eb384166bd773d1099feb7cf165f7eec01936 [diff] |
Add an integration test that setup the jenkins cluster using Docker Right now this test just verify that some jobs answer 200 OK but we can add more stuff later. Note that each new test can adds a second or more (let say if we actually trigger a build) but launching the jenkins cluster takes at least 45seconds on my laptop, so it is worth putting more stuff in one tests before sharding it. Change-Id: Ia3a6b0dbad3821e36fa8c0d49a1ebfb2b9343c05
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.