commit | 0466f770180901ac17e00758b00c98fb5a1851cc | [log] [tgz] |
---|---|---|
author | Klaus Aehlig <aehlig@google.com> | Thu Jun 08 11:19:32 2017 +0200 |
committer | Klaus Aehlig <aehlig@google.com> | Thu Jun 08 13:41:07 2017 +0200 |
tree | 0b5d82840389b9a699e4a36ab2f2a3d9be62c2cd | |
parent | bae7f95426892bc6b0c3cf1b1eb56d07c0021488 [diff] |
Ensure our jenkins-slave startup script terminates ...by properly daemonizing the jenkins job. In this way, all startup jobs terminate (after starting their respective daemons), and we no longer depend on that job being started the last. In fact, on some systems, other tasks are only started after after the termination of the startup script---leading to the situation that jenkins works, but, e.g., sshd is not running. Note that still is not the proper way of starting a daemon; a proper integration with the init system would be preferrable. As, however, those differ between the various Unix-like systems, and we need to work for all of them, this is a good trade-off. Change-Id: I06653184ad09c547572c4744aaf74bd33ed1c9a5
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.