diff options
| author | Oliver Smith <osmith@sysmocom.de> | 2022-12-21 19:05:32 +0100 |
|---|---|---|
| committer | osmith <osmith@sysmocom.de> | 2023-01-16 15:19:29 +0000 |
| commit | f997b4e7712b65175deaf5ab13df0f568ae6f091 (patch) | |
| tree | f170a8f500b67128ca4c61338056c73affeb4d99 /ttcn3-bsc-test/jenkins.sh | |
| parent | 4cb0fac1b0e18b8036cea66225681160561f422d (diff) | |
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
Diffstat (limited to 'ttcn3-bsc-test/jenkins.sh')
| -rwxr-xr-x | ttcn3-bsc-test/jenkins.sh | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/ttcn3-bsc-test/jenkins.sh b/ttcn3-bsc-test/jenkins.sh index 2138169..149e0d1 100755 --- a/ttcn3-bsc-test/jenkins.sh +++ b/ttcn3-bsc-test/jenkins.sh @@ -23,8 +23,8 @@ cp osmo-bsc.cfg $VOL_BASE_DIR/bsc/ mkdir $VOL_BASE_DIR/bts-omldummy -SUBNET=2 -network_create $SUBNET +network_create +network_replace_subnet_in_configs echo Starting container with STP docker run --rm \ |