Commit Graph

110 Commits

Author SHA1 Message Date
Harald Welte 5a76f11320 ttcn3-bsc-test: Fix log file name (osmo-bsc.log, not osmo-msc.log) 2018-02-14 09:06:03 +00:00
Harald Welte 675c76cfd5 ttcn3-bsc-test: Update config with recent changes (VTY, moduleparm change) 2018-02-14 09:05:35 +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 9efd75aa44 bsc-test: omldummy now has an argument for number of TRX 2018-02-06 20:30:08 +01:00
Harald Welte 6e61e5a319 bsc/msc test: Make sure we create text log files
as we don't capture stderr on all *but* the tester container, let's
make sure we write log files from the BSC/MSC/STP containers
2018-02-06 20:22:39 +01: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 f83fe4c7cb ttcn3-bsc-test: Add missing 'git fetch' 2018-01-27 20:25:10 +01:00
Harald Welte 1ab46eadc8 osmo-bsc-tests: Remove obsolete VTY config statements 2017-12-20 02:35:29 +00:00
Harald Welte 084967574e add ttcn3-bsc-test container with osmo-bsc test suite 2017-12-17 17:21:04 +01:00