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
Since osmo-gsm-tester.git I364e0859c0851b9167907a4d948b659a0f6a19fb the
example/ directory has been renamed to sysmocom/
Change-Id: I8ca085e02330be51de12066da0555c1bc0c8b767
osmo-bts-virtual fails to start:
Error occurred during reading the below line:
ms-power-control dsp
This BTS model has no DSP/HW MS Power Control support
Failed to parse the config file: '/data/osmo-bts.cfg'
Change-Id: Ic85603db10c11de911d20313caf2f819e92d94d1
As of Change-Id Id965295dfe04f8bd5ce831db70c86f67b8dc290b the
bogus 'NAT' log category has been removed from osmo-bsc.
Change-Id: If02272c08ba2df37d1295d09c104d11f96abbe1e
As of Change-Id Id965295dfe04f8bd5ce831db70c86f67b8dc290b the
bogus 'NAT' log category has been removed from osmo-bsc.
Change-Id: I266d6f6ed54d1457b1ca63b87fc1c29f6dd40caf
As of Change-Id Id965295dfe04f8bd5ce831db70c86f67b8dc290b the
bogus 'NAT' log category has been removed from osmo-bsc.
Change-Id: Ie2afacfc15589c26238214cddc00baaf80e993c1
Since osmo-gsm-tester.git I38bcf6abf789f52c3ed0bee7911567fa872e2491
these features are included and used in the "4g" suite to allow
selecting 4G modems different than srsue.
Change-Id: Ie1942fd661b91218780bc52bb000d192259e2b69
Some days ago the Dockerfile was changed to pull from
debian-stretch-jenkins instead of debian-stretch-build, since the first
one has extra runtime dependencies required by osmo-gsm-tester.
However, the jenkins script is still requiring the old dependency. Let's
update it accordingly.
Change-Id: If33aab60e04da7beb4cd0715d5cb3145c001823a
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
This way one can quickly see if osmo-gsm-tester run fine or an issue
ocurred and logs need to be checked.
Change-Id: I0b267889f403fc1505f9dd859568bc15a120dd81
It's set to /tmp/trial by default for convenience, since it's a
temporary directory and easy to remember and to access. Still, let's
give the opportunity to change it (if user wants it to be stored in
persistent data or if has low amounts of non-persistent memory).
Change-Id: I2a7ea361c6156c97bd8d2d94cf1b6856344d4d9f
osmo-gsm-tester uses also the "inst/" directory, so using that name to
install from cmake is not a good idea here, since they will end up in
the same directory under /tmp/trial/inst.
Also, make sure the temporary install dst directory is removed after
creating the archive, since at that point is no longer needed.
Change-Id: Ib6610487140f0703d5817241bc4a63027696c1d4
osmo-gsm-tester.git/contrib/jenkins-build-srslte.sh cannot be used
because there's a need to split the fetch step from the build step.
That's because we want to fetch in the host (in order to use host's user
ssh key for potential private repos) while still building inside the
docker container, where we have all the dependencies (and where the
binaries are going to be run afterwards by osmo-gsm-tester).
During the changes above it was also noticed that /tmp/trial on the host
got its UID+GID changed (because we switch user inside the container to
downscale privileges). Fix it by chown'ing the directory back to the
host user's UID+GID.
Change-Id: Ia0db8fba840392a0b7883cfc15e45c2e80407a16
That image contains extra runtime dependencies (such as libua5.3) which
may be required by software run by osmo-gsm-tester.
Change-Id: I5c6239e1beb0cdc6d2b1477ddb60d66debe5d1aa
After this patch, one can run osmo-gsm-tester with specific parameters
(debug level, suite and tests to run, etc.) by using
OSMO_GSM_TESTER_OPTS variable:
OSMO_GSM_TESTER_OPTS="-s 4g -t ping -l error" ./jenkins.sh
Change-Id: I2e8ff51a3152125148c6a117a987e8c11a576e1e
Vadim Yanitskiy
Pau Espin
Oliver Smith
Neels Hofmeyr
Harald Welte