commit | 92945f1b8682d8498ec7bb448fb153d5351568d7 | [log] [tgz] |
---|---|---|
author | Philipp Wollermann <philwo@google.com> | Fri Jan 19 14:16:09 2018 +0100 |
committer | Philipp Wollermann <philwo@google.com> | Sun Feb 04 14:22:49 2018 +0100 |
tree | 4cc021e3691d2bfdf89c108d1d5b36eefc308103 | |
parent | ac511a4a44329b38d3769506859235b0c529aa1f [diff] |
Disable automatic registration of pull request hooks. We already set the hook in our bazelbuild organization settings. Change-Id: I3b210872f69a84b89a665ca2aeeab3a6cdb2145a
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.
Finally, our docker rules needs authentication which is configured with the credential helper:
gcloud components install docker-credential-gcr export DOCKER_CONFIG="$(docker-credential-gcr configure-docker | sed -E 's|/config.json .*$||')"
You might want to permanently set your DOCKER_CONFIG
environment, e.g. in your ~/.bash_profile
:
echo "export DOCKER_CONFIG='${DOCKER_CONFIG}'" >> ~/.bash_profile
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.