Commit Graph

5 Commits

Author SHA1 Message Date
Harald Welte 35d2cf3c0f ttcn3-nitb-sysinfo: Fix docker network usage
In d770629280 we broke the
ttcn3-nitb-sysinfo builds when switching to jenkins-common.sh

This commit fixes it.
2018-02-14 21:08:53 +00:00
Harald Welte d770629280 jenkins: Add shared jenkins-common.sh
the common script contains some copy+pasted parts between the different
jobs.
2018-02-06 20:20:49 +00:00
Harald Welte bcc29baf39 jenkins: prefix all container names with $BUILD_TAG
... to make them unique and to allow for multiple tests run in parallel
without any clashes.
2018-02-06 19:57:24 +00:00
Harald Welte facbb6575e move every 'test network' to its own IP address space
Ideally we would want to launch a group of containers with their own
private network segment and use the same static IP addresses in those
isolated networks.

The stupidity of docker is requiring unique IPv4 addresses even on
isolated (!) networks.  This means we have to manually give each of our
test setups a different subnet, and then we can at least run one
instance that test in parallel to at most one instance of each other
test.

If this weird reestriction about unique IPv4 addresses didn't exist,
we could start any number of test runs in parallel.
2018-02-06 19:08:45 +01:00
Harald Welte 9c937dd432 add ttcn3 sysinfo container 2017-08-20 23:38:09 +02:00