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
Maintaining several versions of the same file in different folders
is a bad idea, because at some point their content gets out of sync.
This is exactly what happened to 'respawn.sh': sleep()ing was only
implemented in 'osmo-bts-master/respawn.sh', other versions of this
file would simply ignore '$SLEEP_BEFORE_RESPAWN'.
The easiest solution would be to have all common files in a single
directory, however Docker does not allow to ADD files from outside
of the build context. In other words, all files must be in the
same directory as the Dockerfile itself.
Modify 'make/Makefile' in order to copy the contents of common
directory to the current build context ('pre-build' target) and
remove it after building ('post-build' target).
Change-Id: I3ec86c8610b3b43d39ea8e3da444861d317ced4e
Change debian-stretch-build-dist to be based on
debian-stretch-obs-latest instead of debian-stretch-build. The latter
installs the nightly OBS repository now (as that is what we need for the
TTCN-3 builds using debian-stretch-build), but debian-stretch-build-dist
needs to install packages from OBS latest.
Fixes jenkins failures:
The following packages have unmet dependencies:
libasn1c-dev : Depends: osmocom-latest but it is not going to be installed
...
Related: OS#5049
Change-Id: I2cf6ed732e55b8f0e63bd8fc040749bd16676d0f
The missing dependency is being added to osmo-msc master's
contrib/osmo-msc.spec.in file. Until the next release is done, which
contains the patch, install the library explicitly to fix:
<0009> db.c:648 Failed to create database connection to sqlite3 db 'sms.db';
Is the sqlite3 database driver for libdbi installed on this system?
Related: https://gerrit.osmocom.org/c/osmo-msc/+/23284
Change-Id: I27d4573de22a8e013623ec606e056d348102abd1
In binary packages for Debian, osmo-bts-omldummy is (for some reason)
part of 'osmo-bts-virtual' package. For CentOS this binary is
shipped properly in a separate package, so let's install it.
This change fixes ttcn3-bsc-test under CentOS failing with:
/usr/local/bin/respawn.sh: line 9: osmo-bts-omldummy: command not found
Change-Id: Ibbfd88d914a31dcfd3e33c6025d612d456b6b124
Add liblimesuite-dev and libuhd-dev, so we can successfully build
osmo-trx in docker in master-builds and gerrit-verifications.
Related: OS#5055
Change-Id: Ieec31fd6a2034c4430be81afd1d370816cd577d5
This reverts commit b70b3c1a80110329aa7c6a8be5a9e0ced511be13.t
The patch was merged too quickly before osmo-ttcn3-hacks.git one.
Revert temporarily to avoid all tests failing due to non-existant module
parameter.
Change-Id: I61850cb0ea5ef2a86657dc8390ad7dbcb943b4bf
Move common code from osmo-*-master to debian-stretch-build and
centos8-build:
* add the OBS repository key (debian only)
* add the OBS repository with "nightly" feed (debian only, already done
for centos8)
* install telnet
* invalidate the cache once the repository is updated
While at it, remove deprecated MAINTAINER lines.
This fixes the need to read both the repository index of debian-stretch
and centos8 and having to invalidate the cache if either of them changes
(instead of reading just the relevant index and invalidating the cache
only if the relevant one changes).
A similar change was done with osmo-*-latest in
I443d52eba416ea298cc5421e280ad2f4ca59283b.
Related: OS#5049
Related: https://docs.docker.com/engine/reference/builder/#maintainer-deprecated
Change-Id: Id69f3eaf37f823bac0947366f27a25edd277a4cb
Add a new centos8-obs-latest container with shared code (just like
debian-stretch-obs-latest) and adjust the package install blocks in
osmo-*-latest.
Related: OS#5049
Change-Id: I274b31d4903df07e99fd434af25bdb72991f6923