commit | f139158988aae1577865d5d8b5b11a10bfd18e1c | [log] [tgz] |
---|---|---|
author | Yun Peng <pcloudy@google.com> | Mon Jan 15 13:43:15 2018 +0100 |
committer | Yun Peng <pcloudy@google.com> | Mon Jan 15 14:09:12 2018 +0100 |
tree | a2b0a2d643d5e413e21118c98757a43811cf7aa8 | |
parent | bbd9e6fdebaa034527c7fc34c4401866ad18ba83 [diff] |
Fix tensorflow configuration Run TF build directly using jenkins job configure syntax. No longer run TF tests on Windows, for three reasons: 1. TF doesn't have presubmit for Bazel build yet, so they are easy to be broken 2. TF Tests on Windows requires special setup (build TF pip, install it, and run tests from another directory to avoid python package conflict, not expressible with the json file) 3. It never catchs any actual error from Bazel side. Change-Id: I77e32f2d005fa7f269f2b9f938a439e667b801aa
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.