mongo-db is only available for x86_64 from their third party
repository. Don't attempt to install it for another architecture. As
this is part of the open5gs dependencies, don't install any of them
either.
This should fix the currently failing "update-osmo-ci-on-slaves"
jenkins job. I've considered disabling the build of the osmo-gsm-tester
container for ARM altogether, but the osmo-gsm-tester manual explicitly
mentions ARM trails.
Change-Id: Ieed36b1adf4b9ae147c7ee7ade22d4855c3dbac8
meson from open5gs requires debian10's version. physicial sysmocom OGT
setup already migrated to debian10, do the same here.
Related: SYS#4805
Change-Id: Id329726f93251b617219beeb674046065c30a436
The OGT build setup and the physicial setup use now debian buster. Let's
update this container too to buster to avoid different versions of libs
during build and runtime (such as libasan).
Change-Id: If5adfb3c52ec5ded2adaca984e7a8c05f5866d34
This change employs the same approach as [1] for Release.key.
Change-Id: Ic51d6e6557ee0b56d21d8ff4feaf04bc02e41a2e
Related: [1] I3ec86c8610b3b43d39ea8e3da444861d317ced4e
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
Clone osmo-ci.git, and install all files from scripts/* to
/usr/local/bin. Together with osmo-ci
I45bd7ea56849dab839a98cfd52806f7cd288094e, this will make overwriting
PATH obsolete.
Related: OS#4911
Change-Id: I0820f13cd740f7d4a8999d279cef6ae293a67d81
This allows easily changing to another osmocom repo base URL if the
default one is down.
Related: OS#4862
Change-Id: I8010b08f3dabacfb3c13a44eece6c7a490e0742e
This is needed on the target remote hosts, where osmo-gsm-tester will
install a copy of the script to run remotely at runtime.
Change-Id: I59151dfe7091628707cd016db42171d22729a60c
The python bindings of gnuradio are used to control a zmq connection
broker between srsENB and srsUE to emulate attenuations.
Change-Id: Ic4e8c4d6a5d1e20dd336ff15868c7c3f51dea323
osmo-gsm-tester requires patchelf 0.11 since a while ago to solve some
bugs on older versions. See osmo-ci
d276db78afbb3f28fc6a4a949bca131d0cfac1d4 for more information.
Related: OS#4389
Change-Id: I3a0c2168420d2a4ee2302a191824f571ec17786b
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
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
Since osmo-gsm-tester.git I364e0859c0851b9167907a4d948b659a0f6a19fb the
example/ directory has been renamed to sysmocom/
Change-Id: I8ca085e02330be51de12066da0555c1bc0c8b767
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
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
These are required to allow setting rt prio for jenkins user inside the
docker container, as well as for being allowed to create coredump files.
Change-Id: I8ed6193196d739c1416976d431d07b8a0c55ee2a
* Fix wrong KI.
* Add an extra IP address to slave so that ENB and EPC can be run on
different IP addresses and their GTP ports don't collide.
* Add required rf parameters to resources.conf
Change-Id: I0198bc99f75e9567ee717aa79e434ec28705fac9
Currently srsLTE trials link against soapySDR library to have LimeSDR
support. We need to move installation of those new packages further
below in the Dockerfiler because that lib version is only available with
osmocom repositories (which were added at a later point in the file).
Change-Id: Ia0e506954ffebd94adb75fec6bf481e41f9ec436
This set up allows running a typical osmo-gsm-tester set up with a main
unit (ogt-master) attached to one (or more) slaves where resources are
located and processes are run.
As an example, current config allows running an iperf3 test over an srsLTE
stack using the ZeroMQ backend.
Change-Id: Iac7c0b613048ce332642d3957c55cc7c53b56d42