Changes

jobs/ttcn3: move pgw to testenv

Change-Id: I74ddac6ebf7f2ff61a36aca3458600b696279703

jobs/ttcn3-testsuites-testenv: add email parameter

Change-Id: I92d92daf7ca087cbe25ab8e873b270a6bf9badb1

jobs/ttcn3-…-testenv: add TESTENV_ARGS parameter

Change-Id: I2a07319ee26ac497eff2853329a002cdb09f75b4

jobs/ttcn3-testsuites: add email parameter

Change-Id: I9385f553196ac8d1ac1bfb05735ed937da67b7b4

jobs: add ttcn3-bsc-test-{sccplite,vamos}-asan

Fix that we didn't have asan variants of those two.

Change-Id: I9888ec08bc39baaf713cb0a89d133e10fed50e0d

OBS: use debian/eol:buster for debian:10

Related: OS#6811
Change-Id: I5dabb97e259bd1d84cf6e9f8a46dc17240b5b88d

jobs/repo-install-test: add email parameter

Change-Id: Ief7a800b5bc478adec03db52335965ed0cfa86ae

repo-install-test: debian10: use archive mirror

Related: OS#6811
Change-Id: I5c6d6624c083e103927942f62e76fbb7b87127a8

jobs/registry…: add email parameter

Change-Id: Ie1e258b77ddb988e27b778cb8243cf33bb5f5440

jobs/registry…: debian:buster -> debian/eol:buster

Related: OS#6811
Change-Id: I6a9fdec0fa1063859e10cf5978cf6fd6b53619c1

jobs/registry…: fix syntax error

Use $REGISTRY instead of ${REGISTRY}, so jenkins-job-builder 6.3.0
doesn't interpret it as JJB variable. It needs to be interpreted as
shell variable here. This probably worked with older JJB versions.

/home/user/code/osmo-dev/src/osmo-ci/jobs/registry-update-base-images.yml:27:11: While formatting string 'REGISTRY="registry.osmocom.org"\nIMAGES="\n  debian/eol:buster\n  debian:bullseye\n ...': Missing parameter: 'REGISTRY'
              REGISTRY="registry.osmocom.org"
              ^

Change-Id: I54b11d0dd7847bd208c4e4270be3151479dac983

osmo_git_clone_url(): add logger_gsmtap and enftables

Change-Id: I495f3334a8d61a325fe6540043b07b8dababd8c6

jobs/master-builds: add logger_gsmtap and enftables

Change-Id: I88d8e03770e7effb49e59493d0e9ba59f75e8ddd
Related: logger_gsmtap.git e06a0b9b3506e8ab1a7cfeeae72e32b2d6186989
Related: enftables.git 735602e15471eab82c93f9e2e044a4d69031ced8

jobs/gerrit-verifications: add logger_gsmtap

Change-Id: I4ffae01156caa467ec23f6b89185b8d65d4691a3
Related: logger_gsmtap.git e06a0b9b3506e8ab1a7cfeeae72e32b2d6186989

jobs/master-builds: fix repos_url for enftables

enftables is not in Gerrit, use the Gitea URL instead.

Change-Id: I3a50a4498c22c56129a40e410ab30c0e6bfee1ec
Fixes: 46ad4f8 ("jobs/master-builds: add logger_gsmtap and enftables")

jobs/osmocom-obs-sync: add Debian:13

Related: OS#6826
Change-Id: I5ce1b03bc538481f14642a2ec91877e1848a6539

contrib/obs-mirror/obs-mirror-include: update

Update the daily backup/mirror configuration.

* Add Debian 13
* Add Raspbian 12 (not sure why it was not there yet)
* Add nightly/CentOS_7 (we build a few packages for it and we also have
  the mirror configured for latest)
* Remove CentOS 8 (dropped 1 year ago: https://osmocom.org/news/255)
* Remove Debian 10, Raspbian 10 (https://osmocom.org/news/308)

Related: OS#6826
Change-Id: I88e209d19fbdc65775342769a37600642b570130

OBS: support building debian trixie (13) pkgs

Translate "debian:13" to "debian:trixie", as for some reason no docker
tag is getting pushed for "debian:13". With this we can keep using the
usual short naming scheme in pipeline_binpkgs lines in
gerrit-verifications.yml (see next patch).

Change-Id: I1377af7f74f074ed6e28e07dee82360d024edd05

jobs/gerrit: remove binpkgs that are the default

Remove the pipeline_binpkgs lines that are the same as the default. This
is in preparation for changing the default.

Change-Id: I348a83c8d70c2042bcab9ccaf83be2a638e722e7

jobs/gerrit: binpkgs: update debian versions

Change the default from "debian:10 debian:12" to "debian:11 debian:13",
as Debian 13 has just been released and we are about to remove Debian 10
binary packages.

Related: https://osmocom.org/news/310
Related: https://osmocom.org/news/308
Related: OS#6826
Change-Id: Ifc1d603c9e6e5054ad2f121f53ba3fb7e4d05286

jobs/registry-update-base-images: add debian:trixie

Change-Id: I905863157b35bdc4ca60116be477b90abbd215f1

jobs/osmocom-obs-sync: add email parameter

Change-Id: I4e9b2f474bfd3b5eb235e46475cef54e3fc17aec

OBS: sync_obs_projects: support security.d.o

The Debian 13 meta config in the OpenSUSE OBS now lists
security.debian.org. Adjust the script that syncs the config to support
this URL too, rewrite it to HTTPS just like the other mirror URL.

Fix for:
      changing url to https: http://security.debian.org/debian-security?dist=trixie-security&component=main
  Traceback (most recent call last):
    File "/obs/sync_obs_projects.py", line 322, in <module>
      main()
    File "/obs/sync_obs_projects.py", line 312, in main
      rewrite_meta(project)
    File "/obs/sync_obs_projects.py", line 190, in rewrite_meta
      assert url.startswith("http://ftp.de.debian.org/debian"), \
  AssertionError: unexpected mirror URL

Related: https://build.opensuse.org/projects/Debian:13/meta
Change-Id: Iaf6a025376e398e26c5031b07fee6c1f64cbe047

scripts/obs/sync_obs_projects.py: format with ruff

Change-Id: I1b7281b32c352b09a0641175b6f70751010800d9

jenkins-gerrit: print the URLs this script reads

Make errors easier to understand by printing all URLs that the script is
reading from.

Change-Id: Ic0e7fc0e5a82927fc9ef6ec02c374b1ec7dd73e5

jenkins-gerrit: binpkgs: ignore decode errors

The output of recent osmo-s1gw jobs for building binary packages
contains invalid utf-8 characters, even though it should be utf-8
according to the HTTP header:
  content-type: text/plain;charset=utf-8

We only need to get the distro name from the output here, so simply
ignore any decode errors.

Fix for:
  $ ./comment_generate.py https://jenkins.osmocom.org/jenkins/job/gerrit-osmo-s1gw/417/ -o gerrit_report.json -t result
  Reading https://jenkins.osmocom.org/jenkins/job/gerrit-osmo-s1gw/417//consoleText
  Reading https://jenkins.osmocom.org/jenkins/job/gerrit-binpkgs/17255/consoleText
  Reading https://jenkins.osmocom.org/jenkins/job/gerrit-binpkgs/17260/consoleText
  Traceback (most recent call last):
    File "/home/user/code/osmo-dev/src/osmo-ci/scripts/jenkins-gerrit/./comment_generate.py", line 270, in <module>
      main()
    File "/home/user/code/osmo-dev/src/osmo-ci/scripts/jenkins-gerrit/./comment_generate.py", line 257, in main
      comment = get_comment_result(args.build_url, args.notify_on_success)
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File "/home/user/code/osmo-dev/src/osmo-ci/scripts/jenkins-gerrit/./comment_generate.py", line 198, in get_comment_result
      pipeline = parse_pipeline(build_url)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^
    File "/home/user/code/osmo-dev/src/osmo-ci/scripts/jenkins-gerrit/./comment_generate.py", line 89, in parse_pipeline
      stage = stage_from_job_name(job_name, job_url)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File "/home/user/code/osmo-dev/src/osmo-ci/scripts/jenkins-gerrit/./comment_generate.py", line 59, in stage_from_job_name
      return stage_binpkgs_from_url(job_url)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File "/home/user/code/osmo-dev/src/osmo-ci/scripts/jenkins-gerrit/./comment_generate.py", line 46, in stage_binpkgs_from_url
      content = response.read().decode("utf-8")
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xef in position 237446: invalid continuation byte

Change-Id: If398037272c2de54c359ea8d907b35f6fb1e2b8b

jobs/gerrit-verifications: osmo-ttcn3-hacks: do make clean

It's easy to break the build verification [for everybody] by
submitting a patch that creates a symlink to a non-existent file.
The workspace is not wiped, so the stale symlink remains and results
in failures like this:

(cd sgsn && ./gen_links.sh && ./regen_makefile.sh)
ttcn3_makefilegen: error: Cannot find any source file for argument `NAS_Templates.ttcn'.
make: *** [Makefile:131: _build/sgsn/Makefile] Error 1

Let's invoke the 'clean' recipe before 'compile' to avoid this.

Change-Id: I886a99e7b1e8c42ccc7441685ecd7b2c54d5a7af

jobs/registry-rebuild-upload-titan: use trixie

Switch to the latest Debian release.

Depends: osmo-ttcn3-hacks Ib62851960724c17f9adddf54a2fc39adef911d32
Related: OS#6826
Change-Id: Iecca98c88ca81f192b7ffb01314654e1aa5cdb8b

jobs/ttcn3-testsuites-testenv: pull trixie image

Change-Id: Id6502c8fdad17feca9e3bc22f8b80d238fad9a8d

OBS: lib/debian: format with ruff

Change-Id: I9aeade2c81f9d7bcfe0c04a0b9c75012217af90f

jobs/ttcn3-testsuites-testenv: enable upf latest

All tests are passing with upf latest now, so enable it.

Change-Id: Ia148d627d5f02e165354665e0b1629cf5e3f330a

OBS: --version-append: never override version

We have some branches set up that when pushed to, directly result in
building OBS packages. We append a string to the package version there,
such as ~rhizomatica.testing. The expectation is that all packages built
from that branch have this string in the version.

Recently an edge case was found: when amending the commit of the last
tagged release, e.g. osmo-sgsn 1.12.0, then the generated version is
based on the previous git tag (as the last git tag's commit is not part
of the current branch anymore) while having the newer version in
debian/changelog. This then results in the newer version being used,
without appending the version string:

  osmo-sgsn: WARNING: version from changelog (1.12.0) is higher than
  version based on git tag (1.11.1.20-e000e~rhizomatica.production),
  using version from changelog (git tag not pushed yet?)

While IMHO it is a bad idea to just amend the commit of the last release
instead of making a separate commit, this results in unexpected behavior
so adjust the script to not override the version if --version-append is
used.

Related: OS#5981
Change-Id: I589ceb08b9e1ff2ccdd54e94216b25e1e40f22fe

jobs: run ttcn3-remsim-test-asan with bookworm

The default distribution to run ttcn3 testsuites and SUTs with has
recently been changed from debian 12 (bookworm) to 13 (trixie). Since
then we have seen 27 additional failures with osmocom:nightly:asan
(while osmocom:nightly and osmocom:latest work fine). As the reason for
this is currently unclear, revert to using debian 12 for this job for
now, so this doesn't mask other errors that the job would find
otherwise.

Related: OS#6845
Change-Id: I702770e36b47df0a47bc9a869127d6251290a7e4

jobs/gerrit-verifications: add libosmo-asn1-tcap

Related: OS#6849
Change-Id: Ib67057469e3848fe72b5a03147c3f6d4b62c33c2

OBS: build libosmo-asn1-tcap

Change-Id: I1b2f0a3ced424977f44f97ca4695132d4f57768c

jobs/master-builds: add libosmo-asn1-tcap

Related: OS#6849
Change-Id: If83114f1dfadc2c649ffa9ccb411dbe20c174a30

OBS: disable_manuals: adjust for osmocom-bb

With the related change, we build manauals in the debian package of
osmocom-bb. The osmocom:nightly:asan feed gets built with manuals
disabled. Fix that building the osmocom-bb package in the asan feed
currently fails with:

[  160s] /usr/bin/make -C doc/manuals
[  160s] make[2]: Entering directory '/usr/src/packages/BUILD/doc/manuals'
[  160s] OSMO_GSM_MANUALS_DIR: /usr/src/packages/osmo-gsm-manuals (fallback)
[  160s] ERROR: OSMO_GSM_MANUALS_DIR does not exist!
[  160s] Install osmo-gsm-manuals or set OSMO_GSM_MANUALS_DIR.
[  160s] Makefile:6: /build/Makefile.asciidoc.inc: No such file or directory
[  160s] make[2]: *** No rule to make target '/build/Makefile.asciidoc.inc'.  Stop.

Related: osmocom-bb Ib04160287c98814a6f2ae104197abda563bdd5b9
Change-Id: I88f3291acbf067ab8779b298e828e18eb828a511

Add Ubuntu 25.10, remove 24.10

Change-Id: I4e65f336b4eac3a9f9c7e0a7d3b76f9f499d6d43

OBS: stop building limesuite

Building limesuite is not needed anymore, as it is available at least
since debian 10 in the debian and ubuntu repositories. We have been
building the upstream version without changes.

Related: OS#6855
Change-Id: Id79ccf873fce8b3b4f61bd73ab89d6a95bd105c1

testenv-coredump-helper: remove

After looking at this again, it makes more sense to keep
/proc/sys/kernel/core_pattern as "core" on build4 and build5, which we
use for jenkins jobs instead of installing systemd's coredumpctl and
making all coredumps go through that. The motivation for using
coredumpctl in testenv was that lots of developers may have it already
installed (though I'm not sure about that anymore), and that it gives a
nice API for retrieving the related executable name to a coredump
instead of having to parse the output of e.g. "file".

Using coredumpctl had the disadvantage that coredumps for all other
jobs, such as the master-builds are also caught by that and cannot be
easily placed in the workspace directory. I have started implementing
this by extending testenv-coredump-helper to communicate through a
socket and mounting that socket inside docker containers running
contrib/jenkins.sh (host -> lxc -> docker), and it works, but this
complexity is not useful here.

Instead the related patch will make testenv pick the core files when
coredumpctl is not available, and read the path from "file", making
testenv-coredump-helper obsolete.

Related: osmo-ttcn3-hacks Ia765b01432e4cb4cd36c45de874b966e3ebf55bc
Change-Id: I2959c6e6d97d5691ee2a4ae5d49a351eb5811f10

scripts/wrapper_core_bt_on_error: new script

Add a wrapper script that runs a given program, and checks the exit
code. If it is not 0, and a core file appears, then load the coredump in
gdb and display its backtrace.

Change-Id: I9673abf3ae3b154505ea09237d37d7da4bf5d57f

jobs/master,gerrit: use wrapper_core_bt_on_error

When the exit code isn't 0, find coredumps and display their backtraces.

Change-Id: Idc893969b158e11d5ae17d0c0a05b52e662f8929

jobs/master,gerrit: set CFLAGS=-g

Generate debug symbols, so backtraces from coredumps become more useful.

Change-Id: Ieff8670e376f140a672a800961be753028cf7b6f

jobs/master-builds: rtl-sdr: add jenkins-notifications

Send mails about failures to the jenkins-notifications mailing list, so
they don't go unnoticed.

Change-Id: I9b783181a467a76bc2d11149baf433581c91bd06

scripts/osmo-ci-docker-rebuild: switch to trixie

Depends: docker-playground I1c0efb85324b70b6370ea94f74f440e639442da5
Change-Id: I1497f14e57f9d7b0867368b923c8f8919c72cd76

jobs/gerrit,master: use debian-trixie-build

Change-Id: Id65b7f9045e13bed38c1de514cdd537fac88f60f

jobs/ttcn3-testsuites-testenv: hlr: add -c osmo_hlr

Now that it is also possible to run the HLR tests against PyHSS, add
"-c osmo_hlr" to run the existing ttcn3-hlr-test jobs against osmo-hlr.
I plan to add jobs for PyHSS later in a separate patch.

Related: OS#6862
Depends: osmo-ttcn3-hacks I7a7e709ec02a9bf44343fff4df2861dfe4e1a761
Change-Id: Ic7acd3ca654580aa8e5a52f162f5c9042fc7d09f

jobs/osmocom-obs-sync: add Raspbian:13

Change-Id: Ib308d12cae2def42c3f1892f606e15c8aebfe140

contrib/obs-mirror: add Raspbian_13

Change-Id: I73e0dbb820935be2f2754a2e2b3e6b3bff409552

scripts/reminder-extend-obs-key: fix typo

One year is 365(.25) days, not 356. Fix that the alarm would have gone
off 9 days later than expected.

Change-Id: I8b46b6b18ce1dea01c5c6c0beb4f10e924f8e4bc

Update Release.key for Osmocom OBS

Change-Id: Iaa333c148f01f518178990bc44c822a471dffbb8

jobs/ttcn3-testsuites-testenv: mme: use -c all

Adjust to MME tests now having two configurations in osmo-ttcn3-hacks:

[testenv] Found multiple testenv.cfg files, use one of:
[testenv]  -c emergency
[testenv]  -c generic
[testenv] You can also select all of them (-c all) or use the * character as wildcard.

Related: osmo-ttcn3-hacks I3d84486dd3826d0f60a3c06693118e36b01ecd2b
Change-Id: Id2296c7cfe1660cc443f08efea209f8bf61aa8b6

OBS: let osmocom-keyring not depend on other pgks

The osmocom-latest, osmocom-nightly etc. meta-packages depend on the
osmocom-keyring package. Fix that the osmocom-keyring package was also
depending on these meta packages.

This fixes that when uninstalling all osmocom:latest packages by
removing the osmocom-latest meta package, the osmocom-keyring package
would also get removed. This is undesirable for switching between latest
and nightly, as the osmocom-keyring package must remain installed to be
able to install new packages from the repository (as it has the repo
key).

Change-Id: If8fbbc40ee45e603de281003db2f61dcb7603e7b

jobs/osmocom-obs: build binary packages earlier

We have recently noticed that with current settings the nightly arm
packages have still not finished the next morning. Schedule nightly OBS
packages 2-3 hours earlier to avoid this.

Change-Id: Ief55cab9308503d582fcfe0c602c75bb48be7dae

OBS: lib/srcpkg: format with ruff

Change-Id: I2cfb8fc5bd78449e62526758ddb9263cf3d8ced1

OBS: gerrit_binpkgs: print verbose output

Print all shell commands and their output executed by build_srcpkgs.py
and build_binpkgs.py, instead of only printing them on error. This is
useful to see the output of the scripts downloading dependencies when
building sourcepackages.

Change-Id: Ie1dbde603351b1d26b66f3834b645b1f1f5bbfc8

OBS: build_srcpkg: install rebar3 without apt

Avoid pulling in 600 MB of GUI dependencies.

Related: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1083096
Change-Id: I9a51df03ac173118c35d501bd21c6d023a436844

OBS: set default distro to debian 13

Change the distribution that is used to build the source packages to
debian 13 so we are on the latest one again.

Change-Id: I7c1dcca90e46645a497fd547ce1243b414c53201

OBS: support building pyhss

Build source packages for the python project pyhss similar to how we do
it for erlang projects: by downloading all dependencies ahead of time
and vendoring them in the source package.

Related: SYS#6819
Change-Id: I321090e811f7c5c142bf973c616d83cd5b2219ab

OBS: configure Osmocom pyhss fork

Add the Osmocom fork of PyHSS to scripts/obs/lib/config.py, so the
Osmocom_OBS_* jobs build source packages for it and push them to our OBS
where binary packages get built. We need to use a fork for now, as the
official repository can't run outside of a git tree yet and doesn't have
debian packaging. These changes are being upstreamed, the goal is that
we don't need to use our fork in the long run.

Related: SYS#6819
Change-Id: I8fc7ef9dc242248770711da2893492fae8a84522

jobs/ttcn3: add ttcn3-hlr-test-pyhss

Change-Id: I608f3d7ade5098e7a8f7808ae2b57955c1354c85

OBS: fix building pyosmocom for debian 12

Related: pyosmocom I8416234ea02f337fabd075cc345af964c1b71adf
Related: https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license-and-license-files
Change-Id: Ia8ef3a0301aeaad4691c197ed780e86b497def4a

OBS: sync_obs_projects: fix for OSC 1.12.1

Since the Docker image used by sync_obs_projects was changed from Debian
12 to 13, several "osc" commands have in their output:

  fatal: not a git repository (or any of the parent directories): .git

Work around this by switching to the temp directory and initializing a
git repository there, with an "origin" remote that osc also expects to
exist.

Fixes: 6ac535b8 ("OBS: set default distro to debian 13")
Change-Id: I1236a065e2998fb46343df3968f7bb4dabeea55a

jobs/ttcn3: add -ogs-latest jobs

Be consistent with the Osmocom jobs where we have -latest too.

Add no mail notifications to open5gs maintainers, because if tests start
failing for latest then it usually means a regression in our testsuite
code.

Change-Id: I28c3b7130661c177271d7341f759a05c94d9607f

jobs/ttcn3: add ttcn3-hss-test-pyhss

Depends: I224eb4aa5fec3dc97f6fa956a4a86f206c8b12b7
Related: OS#6862
Change-Id: I517d36d890690e606050158221d2df9028745dae

jobs/ttcn3: adjust to testenv config rename

Replace "-c osmo_{hlr,ggsn}…" with "-c osmo".

Depends: osmo-ttcn3-hacks I7a64c946ece8ad5bfbf4f7d613634138af6db566
Change-Id: I3766d76a5a6fa8a8de00137fe33e0e747337c66e

jobs: libosmo-sigtran: add support for TCAP loadsharing

TCAP loadsharing requires an additional library libosmo-asn1-tcap.
./contrib/jenkins.sh is using the env TCAP={0,1} to select this feature.

Unclear if we should also put it into our default build.

Change-Id: I47c193d8f5ce695fdc6c368eee94d21c5a4b2c6e

lint: run clang-format only on specific projects

For most C projects, running checkpatch works best with the coding style
we use. Run clang-format only in specific projects that seem to be fully
formatted with that tool.

Related: https://gerrit.osmocom.org/c/osmo-mgw/+/41529
Related: https://gerrit.osmocom.org/c/osmo-asf4-dfu/+/39470
Related: https://gerrit.osmocom.org/c/osmo-ccid-firmware/+/39471
Change-Id: I2c07b30f9254b54027b721b77ab6f35249b5e2de

scripts: Add libosmo-asn1-tcap to OSMO_RELEASE_REPOS

Change-Id: I76703ed5c648eb50574166f8459fd0bde1720902

ansible: jenkins: mount tracefs via fstab

Allow using bpftrace inside the jenkins lxc containers by making
/sys/kernel/tracing available through /etc/fstab.

Related: OS#6794
Change-Id: I568e3635fcc33040036fd19e9226b413db0d3ef3

jobs/ttcn3-testsuites: set RUN_BPFTRACE=1

Allow better analysis of instabilities with the ttcn3-bts-test jobs in
jenkins by running bpftrace scripts along with osmo-bts.

Only the ttcn3-bts-test scripts make use of the RUN_BPFTRACE environment
variable, so this does not affect how any other testsuite runs.

See the related docker-playground commit for details.

Related: OS#6794
Related: docker-playground I5c22cdbb08fe797be936ca174f65ade626fa4895
Change-Id: Iaa960772fb0b09722594747006890e5e43752d43

contrib/known_hosts: update gerrit ssh key

Related: OS#6920
Change-Id: I66e5d96dcb34d33a21f5a70899fba9a75e6127ed

scripts/manuals: use debian-trixie-build

Fix that the Osmocom-release-manuals job was still using
debian-bookworm-build instead of debian-trixie-build to build the
manuals. We use the latter for building manuals in master-builds and
gerrit-verifications.

Without this patch building pyosmocom manuals failed with the following,
as python3-typing-extensions in debian bookworm is at version 4.4.0 but
typing_extensions >= 4.6.0 is needed for TypeAliasType. Trixie has
version 4.13.2.

AttributeError: module 'typing_extensions' has no attribute 'TypeAliasType'. Did you mean: 'TypeAlias'?

Fixes: OS#6916
Change-Id: I6ac302c8ea5836c5096f0d8ab36260cc6f7c11d9

jobs/ttcn3-testsuites: disable bpftrace

The bpftrace process doesn't stop properly with some scripts. Disable it
for now, we can still enable it in copies of the job.

Related: OS#6925
Change-Id: I78c18c2e18d66408ac7de7cd24fafdf3f7e5202d

ansible: allow jenkins users to set rtprio 30

Create an /etc/security/limits.d file to allow the jenkins user to set
rtprio 30. This is required for running the ttcn3 bts testsuite through
testenv, as (unlike the previous approach with docker containers)
osmo-bts-trx runs without root rights there.

Change-Id: Id79851b3e3a47d19773aa9bba134b9bf99dbecbb

jobs/dahdi: fix git clones not getting updated

The refspec line has caused the git clones of the linux kernel to not
get updated.

Fixes: OS#6932
Change-Id: Id3b35ac10cf4fcb244c572a319433379e2e59c22

jobs/dahdi: add linux-6.12

Closes: OS#6931
Change-Id: Ia5bd796e1cdf6f0f22fe0cba1546c4487d847c30

jobs/gerrit: debian10 for osmo-gbproxy + deps

Related: SYS#7859
Change-Id: I7ad3412d945de8c29b6ab62fcadfd2f231c19581

scripts/repo-install-test: test osmo-pfcp-tool in latest

osmo-pfcp-tool is available in latest for quite some time now, so adjust
the check.

Related: osmo-upf Icf4bb566d9b627ead370174e92629a9fccde755e
Change-Id: Icca5a31270bca03596be8ed0104bfb7143fb1ede

repo-install-test: debian 10: osmo-gbproxy only

We only build osmo-gbproxy for debian 10, because a customer requires
it. Adjust the repo-install-test to only verify that osmo-gbproxy can be
installed and runs as expected.

Related: SYS#7859
Change-Id: Id8d8cda8e399719f06aeb1843eb8f5ab12a90e8f