aboutsummaryrefslogtreecommitdiffstats
path: root/ttcn3-msc-test
AgeCommit message (Collapse)AuthorFilesLines
2018-02-14ttcn3: Add OSMO_TTCN3_BRANCH build-time argument to build non-master branchesHarald Welte1-2/+4
2018-02-14Use new split config file + tcpdump support of osmo-ttcn3-hacksHarald Welte4-30/+9
This uses osmo-ttcn3-hacks Change-Id I3db452e24e5238aa05254d903739c64d202e61db, which introduces some shared/common config file as well as per-testcase pcap file generation.
2018-02-14ttcn3-msc-test: Update MSC_Tests.cfg (moduleparm changes)Harald Welte1-3/+9
2018-02-14ttcn3-msc-test: Update osmo-msc.cfg to recent master (removed vty commands)Harald Welte1-2/+0
2018-02-06jenkins: Add shared jenkins-common.shHarald Welte1-21/+5
the common script contains some copy+pasted parts between the different jobs.
2018-02-06jenkins: prefix all container names with $BUILD_TAGHarald Welte1-3/+3
... to make them unique and to allow for multiple tests run in parallel without any clashes.
2018-02-06bsc/msc test: Make sure we create text log filesHarald Welte1-3/+3
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-06move every 'test network' to its own IP address spaceHarald Welte5-14/+24
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-01-27Add ttcn3-msc-test container with OsmoMSC test suiteHarald Welte7-0/+266