gr-gsm-master is using it but it cannot be overriden. Similarly iy can
be helpful to do so in temporarliy modified images when testing
libosmocore features.
Change-Id: Ia9f26f3513da339d2255a0f6b2277682fe15bdf2
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
It is needed by some user manuals using code snippet syntax
higlhlighting, such as osmo-gsm-tester one:
"""
[source,python]
----
sleep(3) # sleep for 3 seconds
----
"""
asciidoc: WARNING: test_api.adoc: line 19: filter non-zero exit code: source-highlight -f xhtml -s python: returned 127
asciidoc: WARNING: test_api.adoc: line 19: no output from filter: source-highlight -f xhtml -s python
Change-Id: I8427179f7cfc0c9150e5327803ca89adffedb8f1
The test mentioned above is added in osmo-ttcn3-hacks.git
Ieb7444c6312bbeab64da2732393b3facf3e1f003.
config files are updated to make sense:
* "nominal power" in osmo-bsc.cfg reflects correct default nominal tx
power of fake_trx.
* "osmotrx tx-attenuation" in osmo-bts.cfg is removed to let osmo-bts
use the value received through OML (max_power_red 20).
* "power-ramp step-size" in osmo-bts.cfg is increased to speed up the
test. There's no good reason to keep it lower.
Change-Id: I878d329dde3d2089ee3b68f56271fcb88d210025
This allows easily checking if fake_trx fails to start early during
startup, for instance due to a python exception.
Change-Id: I3e13a3b1f78d071618e4848aa19bcba1eb300d18
By default, Debian's package manager (apt) would install as many
dependencies as possible, including optional (recommended and
suggested) ones.
Package 'eclipse-titan' recommends 'default-jdk', which is
absolutely not needed for osmo-ttcn3-hacks, and in its turn
depends on +100500 more packages like xorg, wayland, etc.
This change significantly reduces total amount of dependencies
and the overall build time by disabling installation of
recommended and suggested dependencies.
Change-Id: I56f0d0f37e212b15e8c19ddea96d1c999177eb17
Unfortunately, we have to revert a part of change [1], because it
broke ttcn3-msc-test-latest. The reason is that the latest release
of osmo-msc does not support 'timer vlr T3212 30'.
Change-Id: Iaeb6f1ffee9286394654bc3cf9d985ace7829110
Adjust the Dockerfiles, so 'docker_images_require osmo-mgw-master-centos8'
etc. result in a centos8 based image. centos8-build already configures the
Osmocom nightly repository, so we only need to configure it for
debian-stretch.
Related: OS#4564
Change-Id: I6579748056ce0505304378b342a698b98c77fd18
Make it possible to call the ttcn3-*/jenkins.sh scripts with:
IMAGE_SUFFIX="master-centos8"
The existing docker_images_require lines of these jenkins.sh scripts
will then call docker_images_require with arguments like
"osmo-mgw-master-centos8". For example, from ttcn3-mgw-test/jenkins.sh:
docker_images_require \
"osmo-mgw-$IMAGE_SUFFIX" \
"ttcn3-mgw-test"
Let docker_images_require build the image from
osmo-mgw-master/Dockerfile (-centos8 is cut off from the dirname) and
with DISTRO=centos8 as argument.
Collisions with the debian-stretch images are avoided by setting IMAGE
to the full image name (e.g. osmo-mgw-master-centos8).
Related: OS#4564
Change-Id: I598a262fe1a7ed4dd89e13c53e4ded103c6e3b91
Prepare for distro-specific osmo-* images. While at it, put each
--build-arg on a separate line for readability.
Related: OS#4564
Change-Id: I1bf1c46295035a073e440faea3696ce53e7d7985
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
Add a function to automatically resolve the most common dependencies,
osmo-* need debian-stretch-build and ttcn3-* need debian-stretch-titan.
Do this in a shell function in jenkins-common.sh, so we can extend it in
the next patch with distribution specific dependencies (osmo-*-centos8
needs centos8-build).
Related: OS#4564
Change-Id: I98760c6dc3206529c0e267338c9f6f8e1d5be33a
Create centos8-build similar to debian-stretch-build, as preparation for
ttcn-3 tests on centos 8.
Related: OS#4564
Change-Id: Ide1e88c92b7ac301f0ea8ca110c1b2eb43f9d5ad
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 is needed for the forthcoming frequency hopping test cases.
Change-Id: Ib5ad31388ae25399ad09739aac3fdcb0b3a1f78b
Depends: I86afb55ecc6703ce7a229aaa626223f9331a4778
Related: OS#4546
Prepare the repo-install-test to be extended to cover centos8 as well.
The scripts from docker-repo-install-test will be moved to osmo-ci.git
as shared code, and extended to work with centos8 too (using this new
image) in I399360ee6389591180859b52f0ef08883447b90b (osmo-ci).
Related: OS#4563
Change-Id: I50743c304728444ede8e0d40b8abef9d17c44d8d
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
Since osmo-gsm-tester.git Change-Id Ieca65b71b543c44cfcec8e83efd0fe053c432e55,
the -c parameter holds the config file and not the directory where it is contained.
Change-Id: I5aa0507d0e82616ee3cca74573fea6bdb7459b53
As of osmo-gsm-tester.git Change-Id
I7eb69f870d0dcb5906d45ae067d6bed1aabf5862, the enviornment variable
OSMO_GSM_TESTER_CONF is deprecated in favour of already existing -c cmd
line argument. Let's use it while still providing the docker setup with
a way (using same env var name) to modify where the conf dir is to be
found inside the docker container (for instance, to provide an external
conf dir).
Change-Id: I54ea9dc4d0bb205debf312f5a37053bc60cfcdb7
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
Fix error after DGSM-related patches were merged:
osmo-hlr: error while loading shared libraries: libosmo-gsup-client.so.0: cannot open shared object file: No such file or directory
Change-Id: I80554fdbfd2c518868485f84a46c56df985c671c
This can serve as an entrypoint for running open5gs-pgw inside
the open5gs-master container. It will run setup.sh to create the ogstun
device, followed by running open5gs-pgwd as 'osmocom' user.
Change-Id: I4527b5e328fb248552e69961b80b9f791ec74293