Support for bundling Chromium unittests into a tarball.

blimp/Dockerfile

Index: blimp/Dockerfile
diff --git a/blimp/engine/Dockerfile b/blimp/Dockerfile
similarity index 70%
copy from blimp/engine/Dockerfile
copy to blimp/Dockerfile
index 3a8004a54383bd26cb1413b066424ce6abc5310e..ab0ce787299bf5eec78bb979d07106ff6903710f 100644
--- a/blimp/engine/Dockerfile
+++ b/blimp/Dockerfile
@@ -9,18 +9,15 @@ RUN apt-get update && \
 
 RUN apt-get update && apt-get install -yq stunnel4 wget
 
-RUN mkdir /engine
+RUN mkdir /out
+RUN mkdir /out/test

[Sriram, 2016/06/02 19:55:05]

could use "mkdir -p" to create all parents as well.

Also any reason to have /out/test instead of say /tests? 

[Jess, 2016/06/02 23:02:14]

Done.

Mostly because I structured this based on how I could get tests running locally.
 My test binaries were looking for data files 2 directory layers under
themselves.

 
 RUN useradd -ms /bin/bash blimp_user
 
 # The glob below expands to all files, but does not add directories
 # recursively.
-ADD * /engine/
-ADD gen/third_party/blimp_fonts /engine/fonts
-RUN mv /engine/chrome_sandbox /engine/chrome-sandbox
-RUN chown -R blimp_user /engine
+ADD * /out/test/
+RUN chown -R blimp_user /out/test
 
 USER blimp_user
-WORKDIR "/engine"
-
-ENTRYPOINT ["/engine/start_engine.sh"]
+WORKDIR "/out/test"