| commit | 2624767fc8db6ca11e727038ca019fa86e814aaf | [log] [tgz] |
|---|---|---|
| author | Damien Martin-Guillerez <dmarting@google.com> | Tue Oct 10 15:24:52 2017 +0200 |
| committer | Damien Martin-guillerez <dmarting@google.com> | Tue Oct 10 14:07:19 2017 +0000 |
| tree | a4f018a6d5a4090a592d9975a4476c83d40d43a0 | |
| parent | f170a297bf5c16bdc576c56875ee28fe7b425c6b [diff] |
Only do full name matching of the machine By quoting the label name and removing any quote character in it. Change-Id: I34196fcfd59521afefe7628458b705a1a0350227
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.