1
0
Fork 0
mirror of https://github.com/moby/moby.git synced 2022-11-09 12:21:53 -05:00
moby--moby/project/make
Tianon Gravi ed345fb18e Run tests in stricter environment
Use `env -i` to very explicitly control exactly which environment variables leak into our tests.  This enforces a clean separation of "build environment knobs" versus "test suite knobs".

This also includes a minor tweak to how we handle starting our integration daemon, especially to catch failure to start sooner than failing tests.

Signed-off-by: Andrew "Tianon" Page <admwiggin@gmail.com>
2015-02-18 23:30:43 -07:00
..
.dockerinit
.ensure-busybox
.ensure-emptyfs Change emptyfs path in integration-cli tests 2015-02-12 15:02:18 -08:00
.go-compile-test-dir
.integration-daemon-start Run tests in stricter environment 2015-02-18 23:30:43 -07:00
.integration-daemon-stop
.validate
binary
cover
cross
dynbinary
README.md [trivial] changed ./hack to ./project in README.md 2015-02-13 18:11:16 +03:00
test-docker-py Run tests in stricter environment 2015-02-18 23:30:43 -07:00
test-integration
test-integration-cli Run tests in stricter environment 2015-02-18 23:30:43 -07:00
test-unit Run tests in stricter environment 2015-02-18 23:30:43 -07:00
tgz
ubuntu
validate-dco
validate-gofmt
validate-toml

This directory holds scripts called by make.sh in the parent directory.

Each script is named after the bundle it creates. They should not be called directly - instead, pass it as argument to make.sh, for example:

./project/make.sh test
./project/make.sh binary ubuntu

# Or to run all bundles:
./project/make.sh

To add a bundle:

  • Create a shell-compatible file here
  • Add it to $DEFAULT_BUNDLES in make.sh