it has been deprecated in libosmocore.git 2.5 years ago:
commit 7e0686c6b4b456ec4e6e15689694b1bcf96c301f
Author: Neels Hofmeyr <neels@hofmeyr.de>
Date: Mon Sep 10 20:58:52 2018 +0200
Change-Id: Ia6946fae497319a894d4e664ac8642340620822e
This param is true by default and there's no one setting it to false
anymore (and soon will be removed).
Related: OS#5042
Change-Id: I1780320c69ec4a9f086677fd4884dec674f8332e
This param is currently set to true by default and will be removed soon.
Related: OS#5042
Depends: osmo-ttcn3-hacks.git Change-Id I4e2049c109986906d3c985ca2282174b1abff581
Change-Id: I3c7e7dc985a339d884dc388b33bf8a6ec986c5b7
Abort the script and trigger the clean up script, whenever any of the
commands below to prepare the testsuite are failing. This saves time
with figuring out why suddenly all or most tests are failing, and avoids
running the entire testsuite on jenkins if it's obviously not going to
work.
Related: OS#3208
Change-Id: Ie68da2affda8c96b3a515a857a921a05f1bf8ef7
Add set_clean_up_trap() in jenkins-common.sh and run it at the beginning
of the jenkins.sh files. Move the common clean up code from the end of
every jenkins.sh file into clean_up_common(), which gets called by the
trap. Add a custom clean_up() function to those jenkins.sh files that
need additional clean up.
Replace explicit container stop commands (for containers attached to the
docker network) with one call to network_clean() in clean_up_common(). It
kills all containers attached to the docker network.
The motivation for this change is the upcoming optional build of initrd
and kernel during ttcn3-ggsn-test/jenkins.sh. After building these, a
short smoke test will be performed to make sure we can boot the kernel
and initrd, before continuing to run the entire testsuite against it. If
building or the smoke test fails, we must do a proper clean up of the
network and fix permissions.
Related: OS#3208
Change-Id: I807c6221d22fec31db23e2516e477a3eb43347fb
These changes are no longer needed since master versions of whole CNI
have been recently released.
Related: OS#5042
Change-Id: I6f491b58d4576b22c8ff3ab56a7b9e17163a8739
Allow jenkins to fetch the image from our private docker registry.
Outside of jenkins, the image is built locally just like before.
Related: OS#5017
Change-Id: I46cc176ea09d8badc359b627d7ce2f459211258c
While I'm at it with tidying up the Dockerfiles, create a
ttcn3-docker-run.sh with shared run code.
Related: OS#5017
Change-Id: Id90769707158f0488eca2313c57b99ea7a4a27c8
Create symlinks to ttcn3-*-start.sh and ttcn3-*-stop.sh in the
prepare.sh script instead of in each of the ttcn3 Dockerfiles.
Related: OS#5017
Change-Id: I634cf71cff7936efe6e0461d21dc1119de922ada
Move the git fetch/checkout code and make call to build the testsuite,
to debian-stretch-titan/ttcn3-docker-prepare.sh. In the next patch, I
will extend the script to update deps right before building too (e.g.
because OSMO_TTCN3_BRANCH changed).
Related: OS#5017
Change-Id: I4b5bedf058dc527e821f9b7204c632820e671af9
Clone the osmo-ttcn3-hacks and all dependency repositories less often by
moving related commands to the shared debian-stretch-titan image.
Remove the 'git checkout -f -B master origin/master' line, because the
master branch is checked out by default.
While at it, move the shared "git config" commands too, and move them
before cloning the repositories, so they don't run again whenever the
deps change (logic to invalidate the cache if deps change will be added
in the next patch).
Related: OS#5017
Change-Id: I2bb142dce061eba4b6a828c4e435510e309989fd
Remove leftover from old TTCN-3 build scripts, before refactoring ttcn3
Dockerfiles. This line has already been removed in 357ec806 from 2017 for
ggsn-test.
In osmo-ttcn3-hacks.git, this is only referenced in the obsolete
bin/install.script (looks like we could remove that, together with the
rest of the bin dir?).
Related: OS#5017
Change-Id: Id23e7fae58ba246916a38aa0a10035d4f67f7588
This part is missing from the already merged
I3394f391a6068ab8afeafa329b69a8ae4ad05cd9
which enabled LCS tests for osmo-bsc.
Change-Id: I873d6e46e00ee0e91b15d719829baff2bf9f115a
Notably LCS tests are still disabled, just routing BSSMAP-LE/SCCP via STP to
the virtual SMLC is now possible.
Change-Id: Ic296291886ce18fd3ff34d45c519de605ba827cc
Introduce this switch for enabling the Lb interface startup, and first off set
to false everywhere. A later patch will enable Lb where it makes sense.
Depends: Idf463c3c2169cad953b4ebc5b5845b31d5efb848 (osmo-ttcn3-hacks)
Change-Id: Id26064931c482c25217bccdeec866e9afc1fd9b5
Adjust osmo-bsc.cfg to work with osmo-bsc
Icaa2775cc20a99227dabe38a775ff808b374cf98 and osmo-ttcn3-hacks
I7eea0dd39de50ed80af79e0f10c836b8685d8644.
Related: Icaa2775cc20a99227dabe38a775ff808b374cf98 (osmo-bsc)
Related: I7eea0dd39de50ed80af79e0f10c836b8685d8644 (osmo-ttcn3-hacks)
Related: OS#4702
Change-Id: I9e9760121265b3661f1c179610e975cf7a0873f1
We previously only allocated IPv4 sub-nets to the network segments
created with 'docker network'. Let's fix that by assigning both
IPv4 and IPv6 address ranges to each docker network.
Related: OS#4700
Change-Id: I8802208fddcce1ffa57e5626575d23d02b320d99
Fix the TC_si2quater_* test fallout.
When adjusting the bsc AoIP test config, forgot to also adjust the SCCPlite
test suite config, which caused fallout in the SCCPlite tests.
Related: Idbcc703ace7012fb395f0eef3e445df28b368d74 (docker-playground)
Related: Iac46ee2cc5bc0978d5f5baa550baf493a7c56b1b (osmo-ttcn3-hacks)
Change-Id: I810ff6f89d722e7274046c360a2cbebf6f6ee53a
The bsc/BSC_Tests_CBSP.ttcn rely on a configuration where the first three BTS
carry out SMSCB messaging, and the fourth BTS does not. That requires a CBCH
channel config on bts 0, 1, 2.
Related: Iac46ee2cc5bc0978d5f5baa550baf493a7c56b1b (osmo-ttcn3-hacks)
Change-Id: Idbcc703ace7012fb395f0eef3e445df28b368d74
Adjust the SCCPlite osmo-bsc.cfg according to changes applied in osmo-bsc.cfg,
which were obviously forgotten to also apply to the SCCPlite test runs.
Do the same logging in both SCCPlite and AoIP osmo-bsc.cfg.
Change-Id: I4a8fe459ec580078228c6775df357b6e0acbbb03
When launching osmo-stp-master from ttcn3-bsc-test, set ulimit=-1 to allow core
files.
In osmo-stp-master set WORKDIR to /data to hopefully get the core file ending
up there without the need to set a /proc/sys/kernel/core_pattern globally in
the jenkins slave.
Change-Id: Idd67fcb3f564b9cff9b4596bf639ed1bd1b58daf
Adjust the SCCPlite osmo-bsc.cfg according to changes applied in osmo-bsc.cfg,
which were obviously forgotten to also apply to the SCCPlite test runs.
Make the SI2quater config reflect that of the AoIP osmo-bsc.cfg.
Change-Id: I4dbabcc28309424a336d2a052a067484d17663ac
Adjust the SCCPlite osmo-bsc.cfg according to changes applied in osmo-bsc.cfg,
which were obviously forgotten to also apply to the SCCPlite test runs.
These handover config changes should fix the TC_ho_* tests in
ttcn3-bsc-sccplite.
Change-Id: I9694863b2db6be6384d1d6ffb35fc477fe774d02
Forgot to also adjust the SCCPlite structure in previous commit
c7b52048e6, which broke SCCPlite testing.
Change-Id: I923e398ccd4bdd31c8325de1a850fe4c3236db79
This only enables ttcn to be able to connect multiple MSCs. To be able to use
this in the BSC_Tests, osmo-bsc.cfg needs adjusting in an upcoming patch; tests
using this are in osmo-ttcn3-hacks I21cbab193cd0de2e5692665442eae113d5f61904.
Depends: Ibb36695b7c31f7b04eec6c5d59522fc0779b3c2f (osmo-ttcn3-hacks)
Change-Id: I1986e4ef43beee161c82193694421b56136c1afe
Don't list debian-stretch-build and debian-stretch-titan as dependencies
anymore, now that docker_images_require finds them automatically.
Related: OS#4564
Change-Id: I3cb6b693f3dd9df84fb29c0217bb3dae454cc18f
EGPRS Packet Channel Request cannot be enabled in 'GPRS only' mode
anyway. Moreover, this command was deprecated. Let's just remove it.
Change-Id: I03733490d9c4bf78a748d22874e550e015fbab78
In the recent osmo-bsc master, this configuration parameter has
been removed, so it fails to start due to "unknown parameter".
Change-Id: I8f763a4b35f80f4db637bebdd8e802a835a9fd2d
This configuration option is unused. Related: the IMSI filtering access list is
being dropped from osmo-bsc, which might cause test fallout.
Related: I89727af5387e8360362e995fdee959883c37d89a (osmo-bsc)
Change-Id: Ied8d766ba230b93cb1185fc8b1a77f5540dfdbc1
osmo-bsc does not use an rtp-base for years, ever since we're using an MGW.
Related: Id14fa3066ca5d472a817593074a6222f159168a8
Change-Id: I267840ecb816e9de6d89ebbacb3e296c59fad57c
Allow to pass options to each "docker run" line in the various
jenkins.sh scripts. I'm using this to run the testsuites and Osmocom
components in docker with the same configurations as jenkins, but with
Osmocom and testsuite binaries built outside and mounted into the
containers:
DOCKER_ARGS="-v /usr/local:/usr/local:ro -v $hacks:/osmo-ttcn3-hacks:ro"
This allows very short test cycles without a second set of configs. The
full script that makes use of this feature is in osmo-dev.git,
ttcn3/ttcn3.sh.
Change-Id: I8d1f78aee926f8f6ec0b704e16639bc83f525816
As of Change-Id Id965295dfe04f8bd5ce831db70c86f67b8dc290b the
bogus 'NAT' log category has been removed from osmo-bsc.
Change-Id: Ie2afacfc15589c26238214cddc00baaf80e993c1
for some strange reason, the tests developed + merged in September 2019
are not yet automatically executed. Let's fix that.
"latest" should work fine, the BSC side code was already present in 1.6.0
Change-Id: I4408265d1be900359256f5cab553893d03cc8362
The logging categories cc and mgcp are obsolete. The tests still contain
logging statements with those categories, which makes osmo-bsc
terminate during startup while parsing the configuration file.
Change-Id: Ifd6bf46b73420c0443f997ea953318710544b751