Building debian-stretch-jenkins on ARM currently results in a few
libraries getting installed for the i386 architecture. This results in
the following build failures for master-osmo-trx and master-osmo-pcu:
checking for LIBGNUTLS... no
configure: error: Package requirements (gnutls >= 2.12.0) were not met:
No package 'gnutls' found
It is weird that we are only seeing this now, the dpkg-line has been in
debian-stretch-jenkins since the Dockerfile was added to osmo-ci four
years ago in Icb0406f96b0c18e77be51ad8317c2668fb23a45e. I'm also
wondering why it was added in the first place, and if we need it
anymore. In any case, running this on anything but x86_64 does not make
sense, so disable it there.
Change-Id: I8d890b7ebc7b99a4c79779709d1e56e0a5a6d4b9
The purpose is to run osmo-ttcn3-hacks/bsc/BSC_Tests_VAMOS.ttcn with
osmo-bts-omldummy -f VAMOS
(send BTS_FEAT_VAMOS = true).
Change-Id: I2146388bf683cfba99cef5592b8b141c3a6eabb1
Adjust docker_depends and docker_dir_from_image_name for 2021q1. Extend
README.md with examples.
Related: SYS#5370
Change-Id: Icf1e3f1928658ff3d82190c4176252cf3590a1f5
Make it possible to set a different mirror for debian-stretch-titan than
for all other containers. 2021q1 doesn't have the eclipse-titan package
and it doesn't make sense to build it there.
I've thought about adding OSMOCOM_REPO_TESTSUITE_PATH and
OSMOCOM_REPO_TESTSUITE_VERSION too, but we don't have any use for these
right now. Let's add them later if we should need them.
Related: SYS#5370.
Change-Id: I7187473c2188a864b60b03789eff62e0a527404a
Allow to change the path between OSMOCOM_REPO_MIRROR and
OSMOCOM_REPO_VERSION. While at it, tweak related comments (comment above
the variable as usually, replace "repo" wording with "feed" for the
latest/nightly variable as we usually refer to it as feed), and mention
OSMOCOM_REPO_* in README.md.
In order to be able to use a different mirror for testsuite and systems
under test, the testsuite related Dockerfiles (osmocom-bb-host-master,
debian-stretch-titan) are not using OSMOCOM_REPO_PATH. We could add a
OSMOCOM_REPO_TESTSUITE_PATH on demand, as mentioned in the next commit.
Related: SYS#5370
Change-Id: I8010a4d49d4620a5c47c2ff4f909a9aeeaad7b73
Add new container to be used by osmo-ci
Icc89e20950c2aaa67b209340d1d797b76fce32d2.
Related: SYS#5370
Change-Id: Ibb55ad18d2ccf4313f52fa3e3c10d4420c84dced
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
Otherwise it will try to connect to 127.0.0.1.
Fixes jenkins ttcn3 test TC_sns_1c1u_unconfigured_nsvc.
Change-Id: I4b375a60c4f948c282337ca30643d14407f8239e
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
When testing gbproxy with an IP BSS, we want to use IP-SNS as that
is the more relaistic use case in practice.
This un-breaks the dockerized tests since I90bd101096979b170c38fa2a80abb80d296c4d2e
was merged in osmo-ttcn3-hacks.git
Change-Id: Id1324e019b7f148f8d33977c0089e996089e1e59
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
In docker-playground.git I272e43b9be8ba53d8a815e8ab099c939f63413a7
we introduce FSM state introspection and we need to add the CTRL
hostname here.
Change-Id: Idcd77353a661cfc1685ded64b5993ff63637addc
Display an overview of installed Osmocom packages at the start of each
ttcn3-*/jenkins.sh script (and others making use of
docker_images_require).
Closes: OS#5091
Change-Id: I62670017d790fd67c6a0d8d464386c0f8e94c1a8
I used this one for building old OsmocomBB branches, which do not
compile with modern arm-none-eabi-{gcc,binutils,newlib} toolchain.
Change-Id: Ide93843836f059a3750e92a973d0a6d9cf9a5638
... which requires some modifications to osmo-ns-master
regarding pipework / docker-entrypoint.sh
Change-Id: I418f81eb1fbb2b15335ef64a3aa04d1c98a452c9
Related: SYS#5396
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
It will be used by osmo-gsm-tester docker image right now, and at some
point in the future jenkins nodes will also migrate to it.
Change-Id: Ibfdec6007357a90212dea7d39300f04ce8ffdf65
Command line argument '-i' has been deprecated.
Change-Id: Ib01069a55a27e79c67b76abe39763c1b645075e5
Related: I17676a21c4e0c9cbc88f2c5c53a39c6c6c473ca1
+ docker container rm jenkins-ttcn3-fr-test-109-frnet jenkins-ttcn3-fr-test-109-ttcn3-fr-test
jenkins-ttcn3-fr-test-109-ttcn3-fr-test
Error response from daemon: You cannot remove a running container 4f5ec7f412b2d37d00b2738b2bcddffada36efebfe7ce32ed196543ee436154e. Stop the container before attempting removal or force remove
Change-Id: I66ed0d073bdd6962f78da54232d6bc58adc09e2c
In I3ec86c8610b3b43d39ea8e3da444861d317ced4e the container-individual
respawn.sh has been replaced with a common one - but unfortuantely
missing to update the debian-stretch-build, which made (at least)
ttcn3-bts-test builds fail for two nights now.
Change-Id: I15dcfe317d7ba81b9df0b5ceef142f4eae1ef3f3
This change employs the same approach as [1] for Release.key.
Change-Id: Ic51d6e6557ee0b56d21d8ff4feaf04bc02e41a2e
Related: [1] I3ec86c8610b3b43d39ea8e3da444861d317ced4e
Oliver Smith
Neels Hofmeyr
Vadim Yanitskiy
Daniel Willmann
Pau Espin
Harald Welte