Since osmo-bts.git a2dc808acc5b99122e97c9013cb1ec2ae0c4a2a1, osmo-bts
depends on libosmo-netif. Let's add the dependency when building.
Change-Id: If033ed7f25bb69a66ecff56b2a1781d6339a6d7e
When downloading the deps/Makefile, use gitea instead of the obsolete
and now defunct cgit deep-link
Change-Id: Ifbcb992e70a1faefc3829df28f8bf4dfaf2143e1
Related: OS#5670
This feature is used to indicate to the BSC that the BTS supports Osmux.
Requires: libosmocore 18c6a8183f92915e77368ecffb1cbf7f555453a3
Related: SYS#5987
Change-Id: Ia402b7514b636750442d0859d5ebc3fcad67dd9f
Use debian:bullseye instead of debian-bullseye-build. Building the
latter requires a lot of time, it's definitively not needed for just
running chmod. Use debian:bullseye, since we use it as base for most
images and it's therefore very likely that it's already downloaded
(and if not, it would get downloaded here).
Change-Id: I88f513a0a8ee04628842a7aa1b663c390d2032cd
New changes in ttcn3 also test SBcAP and CBSP links as client mode in
osmo-cbc.
Related: OS#4945
Requires: osmo-ttcn3-hacks.git c832c10b28c70f244423143f133cf63aea937997
Change-Id: I14a50d3d2284ceffc0607880fecddbff2a048284
This category prints incredibly large output of ASN1c encoder/decoder,
which clogs the logging subsystem while debugging general issues.
Since the encoder/decoder is somehow determenistic, let's disable
logging all the debugging; it can be enabled by the user when
specifically debugging any enc/dec related issue.
Change-Id: I53cc2fe717fa70a8f187788fc4d31d28e0d4e98a
This is intended to ease adding new emulated MMEs and BSCs by using next
available port strting from the one defined in the TTCN3 test module
parameter.
Requires: osmo-ttcn3-hacks.git Ib443aba9396aebe0a56b1a79719bbcf66302a1aa
Change-Id: Ib1387284c8f361572057b6d036429366238382a6
TCP/SCTP client support was added recently in osmo-cbc. Since then, the
connection mode (client|server|disabled) needs to be specified in the
config. Let's update osmo-cbc.git to provide the correct info in here.
Requires: osmo-cbc.git Change-Id I3ec54b615b41b56f7a9c64298e3fcaac37f4b60e
Change-Id: I2e3a806a8371011cdb4c3b1f194e132d3896374e
This is the new expected working order.
Related: osmo-cbc.git I7623ea5874552e57764327e94a9c3a4de7b71d67
Change-Id: Ia6f9cb6ac5935b8253521a6bfe11e6905e77523d
* 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
Do not set up the Osmocom repository inside osmocom-bb-host-master, it
is done in debian-bullseye-build. Without this patch, we actually
installed the debian 9 version of libosmocore-dev in the debian 11
container.
This is part 1/2 of fixing TTCN3-centos-bts-test, which has been failing
since OSMOCOM_REPO_MIRROR was changed in osmo-ci.git. Part 2 is in
osmo-ci I8201f34a0f9747eea78c358a626cc3981d7407c4.
Change-Id: I78e0445a1b82e5cd72ecaa86e8fe25516b19f485
As required by libosmocore, e.g. when building programs directly in this
container with osmo-dev.git/ttcn3/ttcn3.sh.
Change-Id: I4cd05ef2c164dfb765ee365ab38b8dfd4f955ac6
Add arguments to osmo-bts-omldummy to properly report the features that
were previously assumed for osmo-bts even without reporting them, until
this was changed in osmo-bsc I7fca42a39a4bc98a6ea8b9cfab28c4bad3a6a0aa.
Related: SYS#5922, OS#5538
Change-Id: Ib22f25431330676d59900de7bfb3d89e7872baf1
The SO_BINDTODEVICE feature (used for VRF) requires CAP_NET_RAW. Since
we run open5gs-upfd as user "osmocom", that seems to be causing some
permission problems under some systems (like jenkins). Let's make sure
we add the capabilitites to the binary before launching it as user
"osmocom".
Change-Id: I51ee6954a6c019a41cfcd50b2d99166316989d9b
Add libelf-dev to be able to build kernel modules with
defconfig_x86_64.
This is an update to commit d6c5c7a034,
which should have not just modified the stretch but also the buster
Docker image
Change-Id: I4c442d86688278ff634a286b98637189eef88bfb
Related: OS#5407
Pau Espin
Harald Welte
Vadim Yanitskiy
Oliver Smith
Neels Hofmeyr