build-and-test.sh: handle non-interactive environments gracefully.

Previously, the first docker run would fail with a short error message:

the input device is not a TTY

Now, if we are running in an automated environment like Jenkins or Circle CI
the interactive option is removed. It is still available, just in case
there is sometimes a reason to run the build interactively.

Signed-off-by: Jon Seymour <jon@wildducktheories.com>

Author: jonseymour

build-and-test.sh

@@ -2,8 +2,9 @@
 set -e
 VERSION=$(cat VERSION)
 
+INTERACTIVE=$(if test -t 0; then echo -i; fi)
 docker build . -t developmentseed/geolambda:${VERSION}
-docker run --rm -v $PWD:/home/geolambda -it developmentseed/geolambda:${VERSION} package.sh
+docker run --rm -v $PWD:/home/geolambda ${INTERACTIVE} -t developmentseed/geolambda:${VERSION} package.sh
 
 cd python
 docker build . --build-arg VERSION=${VERSION} -t developmentseed/geolambda:${VERSION}-python