Add dockerized ci infrastructure

Change-Id: I30c4a028c75dbbd50675312cea2861fa419c1101
Reviewed-on: https://forge.frm2.tum.de/review/18617
Tested-by: JenkinsCodeReview <bjoern_pedersen@frm2.tum.de>
Reviewed-by: Enrico Faulhaber <enrico.faulhaber@frm2.tum.de>
Reviewed-by: Bjoern Pedersen <bjoern.pedersen@frm2.tum.de>
This commit is contained in:
Björn Pedersen
2018-08-13 14:17:35 +02:00
committed by Bjoern Pedersen
parent 7e54cd93b7
commit 8c5f602a99
3 changed files with 172 additions and 0 deletions

23
ci/README Normal file
View File

@ -0,0 +1,23 @@
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.
(Note: The initial version still has some bootstrapping glue, that will get
changed in a followup).