In various ttcn3-*-test jenkins.sh / Dockerfile:
- add -h (hack) option to jenkins.sh
If calling jenkins.sh with the -h option, bind external osmo-ttcn3-hacks
sources into the docker containers and start a shell instead of the tests:
jenkins.sh -h ~/src/osmo-ttcn3-hacks [bind/this/path/to/src]
An optional second argument is a path bound to /src in the docker image.
- move Dockerfile RUN commands to Makefile within docker img
Add a Makefile to the image's root, move the RUN command there and call that
'make' from the Dockerfile RUN command; allows easy manual invocation.
Change-Id: Id7d47f665828557838f541b4467b713a8605389b
* alpine-*: looks like they were never used
* debian-{jessie,stretch}-*: EOL
* debian9-repo-install-test: EOL
* gitolite: never used? / upstream container last updated 3 years ago
* osmo-gerrit-libosmo: unused example from 2017, based on jessie
* patchwork: looks like never used, ancient version
* public-inbox: added in 2018 for playing around, apparently unused
* tmp: unfinished and unused
* ubuntu-zesty-build: was added for testing ubuntu 17.04, unused
Related: OS#5601
Change-Id: Ic09046379ddff049629bb66850ead7ba479c4450
These files are in .gitignore and get generated at the end of running
'make'. Remove them to have less cluttered 'git grep' output.
Change-Id: Ie5bf05220359ac0941f62cc86ed843363548784a
Adjust the Makefile as well after the docker container has been migrated
to debian 11 in Ib6039724a7200abce5252f95407047296b72cd51.
Change-Id: Ibebca7be7daccd17bbf1b382108d87eb5a93ecf1
Add a jenkins.sh that does the same as the previous lengthy shell
command in the jenkins-job-builder file, and add
osmocom-release-tarballs.sh. This makes it easier to test the
script, and only patching one repository is needed from now on when
changing to a newer debian version.
Depends: osmo-ci I15f6c08b807f1462f91e95b624cdc1aad0592dd6
Change-Id: I4cf66097f508c029f688ec8af1cab2238d42f84f
Let it use debian bullseye and rename the directory once, so we don't
need to rename it in the future when switching the debian version
again.
The reason I'm doing this now is that building with debian 9 failed
due to obs.osmocom.org related changes. It would be trivial to fix that,
but I decided to rather upgrade to the latest debian version.
Change-Id: Ib6039724a7200abce5252f95407047296b72cd51
After switching from build.opensuse.org to obs.osmocom.org's published
packages, the soapysdr0.7-module-lms7 binary package we had does not
exist anymore.
I'm not sure where it came from, from the name it looks like it was
built from version 0.7 sources, but we only have a soapysdr_0.5.4
package in OBS that was added for debian 8/ubuntu 16.04 compatibility 4
years ago, and builds have been disabled for all architectures:
https://build.opensuse.org/package/show/network:osmocom:nightly/soapysdr
Instead of relying on this leftover binary package, use the one provided
by debian instead. This osmo-gsm-tester docker container is based on
debian-buster, which has soapysdr 0.6 packaged. If we should really need
0.7, we could switch it to bullseye or build it from source while
building the container, or add it back to obs.osmocom.org.
I verified that the container builds with this change.
Fix for:
E: Unable to locate package soapysdr0.7-module-lms7
Change-Id: Ie2408258eda407d9db6c2f0f5fbe475861756778
Fix installing packages from https with debian-stretch-jenkins after we
switched the packages mirror to https://downloads.osmocom.org/packages.
Fix for:
E: The method driver /usr/lib/apt/methods/https could not be found.
Related: SYS#5557
Change-Id: I9ece7ffb295d8b371a0000a91b9b6d0f7174535d
Trying to get the gerrit build job for osmo-upf to work,
for patch Ic0d319eb4f98cd51a5999c804c4203ab0bdda650
which adds use of nftables.
Maybe a newer debian version for the docker image may help.
Change-Id: Ieb4fb1ddee80315b547ea7e3405a56fcc41daaad
This is another fixup for [1]. I didn't notice that the sccplite
variant of ttcn3-bsc-test has its own copy of jenkins.sh.
Change-Id: I21219724adbeda4166963b4940b08aad281a62cb
Fixes: [1] Iba4fbd5c9ed59783df4ac64e68b2beef73a812ff
Related: SYS#5460
metrics support using Prometheus has been recently added to open5gs
(28e40a0f1b9048768958344e213c69994be671f5). However, it is still not
enabled by default. Let's enable it and update open5gs config files to
make use of it.
Change-Id: I6ec827d66241e20d631f3a851457921718c168a0
This should have been done as part of [1] in order to avoid
regressions in ttcn3-bsc-test-sccplite.
Change-Id: I2d0045533814a2bacc384c06287066f2209a5f38
Fixes: [1] Iba4fbd5c9ed59783df4ac64e68b2beef73a812ff
Related: SYS#5460
Neels Hofmeyr
Pau Espin
Oliver Smith
Harald Welte
Neels Hofmeyr
Vadim Yanitskiy