commit | 3b8c3b28d70917e2046d36e78c1a120546de6cd1 | [log] [tgz] |
---|---|---|
author | Damien Martin-Guillerez <dmarting@google.com> | Fri Aug 25 11:07:55 2017 +0200 |
committer | Damien Martin-guillerez <dmarting@google.com> | Fri Aug 25 12:23:59 2017 +0000 |
tree | ac7c85ea320f35cffa87f1e1695a0daf0c03a109 | |
parent | b43271b564af07322a70b4bc619f56f0fcc678a9 [diff] |
Increase the maximum number of inodes We got three build that failed due to too many open files on Darwin, increase the limit (see bazelbuild/bazel#2422) Change-Id: I736db4ea0416dcb32a36828a03927d77a74d776e
This workspace contains the setup for the continuous integration system of Bazel. This setup is based on docker images built by bazel.
If you are a user of the CI system, you might be interested in the following document:
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.