Björn Pedersen c0f7034b30 Run publish outside of docker container
Change-Id: I0ac8ee583f305efc7e27155624cfb11e2df8085f
Reviewed-on: https://forge.frm2.tum.de/review/19616
Tested-by: JenkinsCodeReview <bjoern_pedersen@frm2.tum.de>
Reviewed-by: Jens Krueger <jens.krueger@frm2.tum.de>
Reviewed-by: Enrico Faulhaber <enrico.faulhaber@frm2.tum.de>
Reviewed-by: Bjoern Pedersen <bjoern.pedersen@frm2.tum.de>
2018-12-14 13:32:24 +01:00
..
2018-12-13 13:36:23 +01:00

This directory contains the necessary files for running tests inside a docker container.

The Dockerfile defines two images:
- base
  -> this is the image used for testing
- docs
  -> Include a latex install for sphinx pdf builds

(The following assumes you have a docker daemon running on your working computer)

To create the images:

  docker build --target <base|docs> --tag secop_<base|docs>:latest .

To test images interactivly:
  docker run -u jenkins -i -t secop<base|docs> /bin/bash

The Jenkinsfile uses this Dockerfile (only approved checked-in versions from master)
to build the images (a rebuild will only happen if the Dockerfile is changed as docker
 caches the images and build information) and  run the test suite inside the container.