[Skiboot] [PATCH 07/15] travis: move container build into the install step

[Oliver O'Halloran]

Travis automatically hides the output of completed build stages. Moving
the `docker build` output into the install stage results in less spam
to wade through while looking at CI failures.

Signed-off-by: Oliver O'Halloran <oohall at gmail.com>
---
 .travis.yml | 13 +++++++++++--
 1 file changed, 11 insertions(+), 2 deletions(-)

diff --git a/.travis.yml b/.travis.yml
index f34d48d049ad..1ca5dd7cacd2 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -31,9 +31,18 @@ jobs:
     - os: linux-ppc64le
       env: RUN_ON_CONTAINER=docs
 
+install:
+    - docker build --pull -t ${RUN_ON_CONTAINER} -f opal-ci/Dockerfile-${RUN_ON_CONTAINER} .
+    - mkdir -p ci_build_cache/${RUN_ON_CONTAINER}
+
 script:
-    - docker build --pull -t ${RUN_ON_CONTAINER} -f opal-ci/Dockerfile-${RUN_ON_CONTAINER} . &&
-      docker run --volume $HOME/.ccache:/root/.ccache --volume `pwd`:/build --rm -t $RUN_ON_CONTAINER bash -c "./opal-ci/build-${RUN_ON_CONTAINER}.sh";
+    - >
+      docker run
+      --volume $HOME/.ccache:/root/.ccache
+      --volume `pwd`:/build
+      --volume `pwd`/ci_build_cache/${RUN_ON_CONTAINER}:/root/ci_build_cache/
+      --rm -t $RUN_ON_CONTAINER
+      bash -c "./opal-ci/build-${RUN_ON_CONTAINER}.sh"
 
 
 # apparently this needs to be in the master branch in order for it to work on
-- 
2.26.2