docker-playground/ttcn3-pcu-test
Oliver Smith f997b4e771 network_create: find free subnet automatically
Try multiple subnet numbers until successfully creating a network. This
way we can run the same ttcn3 testsuite multiple times in parallel
without conflicts (e.g. once against latest, once against nightly). Also
we don't need to make sure each new testsuite has a unique subnet
number anymore.

I've considered also adjusting network_bridge_create, but that gets used
exclusively by osmo-ran/jenkins.sh, a script which we don't actually run
in jenkins. It seems that in this script it makes more sense to not get
a random subnet number.

Related: OS#5802
Change-Id: I57152b08ef0f38e17e7019a8df032189b03f56cf
2023-01-16 15:19:29 +00:00
..
sns ttcn3-pcu-sns: add vty parameter to allow ttcn3 to connect 2021-04-14 12:42:18 +00:00
Dockerfile Use gerrit as osmo-ttcn3-hacks.git git remote 2022-09-20 12:09:32 +02:00
Makefile make/Makefile: always use docker run --rm 2022-02-14 07:46:23 +00:00
PCU_Tests.cfg ttcn3-pcu: Update config for latest after new osmo-pcu release 2021-11-16 19:12:27 +01:00
jenkins-sns.sh network_create: find free subnet automatically 2023-01-16 15:19:29 +00:00
jenkins.sh network_create: find free subnet automatically 2023-01-16 15:19:29 +00:00
osmo-pcu.cfg ttcn3-pcu-test: osmo-pcu.cfg: use 'gsmtap-remote-host' 2022-10-02 14:44:56 +07:00