Andrei Vagin 9e1c253fe8 gvisor: run bazel in a docker container ... bazel has a lot of dependencies and users don't want to install them just to build gvisor. These changes allows to run bazel in a docker container. A bazel cache is on the local file system (~/.cache/bazel), so incremental builds should be fast event after recreating a bazel container. Here is an example how to build runsc: make BAZEL_OPTIONS="build runsc:runsc" bazel Change-Id: I8c0a6d0c30e835892377fb6dd5f4af7a0052d12a PiperOrigin-RevId: 246570877		2019-05-03 14:13:08 -07:00
..
common.cfg	Configure Kokoro build with RBE.	2018-12-21 15:42:59 -08:00
continuous.cfg	gvisor/kokoro: save runsc logs	2019-05-03 11:21:22 -07:00
presubmit.cfg	gvisor/kokoro: save runsc logs	2019-05-03 11:21:22 -07:00
release-nightly.cfg	Simplify Kokoro configuration.	2018-07-27 17:53:27 -07:00
run_build.sh	Change copyright notice to "The gVisor Authors"	2019-04-29 14:26:23 -07:00
run_tests.sh	gvisor: run bazel in a docker container	2019-05-03 14:13:08 -07:00