Changes

ansible/hosts: add comments with usage hints

When adding build5, these steps were not intuitive so add some
documentation hints about them.

Change-Id: I7b9c14db47d747dab4d96464ab67f4bec5cf9b7a

scripts/repo-install-test: add disconnect hint

Add a hint that would have been useful when we set up build5.

Change-Id: I208cacaaf4018dc3adf5c4b878147c19769381ff

jobs/master,gerrit: use io_uring seccomp profile

Use the seccomp profile not only in ttcn3 testsuites, but also in
master-builds and gerrit-verifications so we can test io_uring there
too.

CI happened to work without this for libosmocore on build4 because of a
specific docker version where io_uring was not yet (fully?) disabled in
the default seccomp profile. It did not work without this patch on
build5 where we currently have a newer docker version.

Related: OS#6405, OS#6186
Related: docker-playground I27567c2a5d9543c3509c316226c082ab950c5ebc
Change-Id: I71df7f7eeb79b831fb67d2cda377cf1d0619b93d

jobs/{master,gerrit}: set ulimit filesize to 1 GiB

Set a max file size limit of 1 GiB via ulimit. This prevents jobs from
filling up the disk by generating one huge log file.

I have chosen 1 GiB as limit, because jobs that clone linux kernel
repos may have packed git artifacts that are several 100 MiB in size.

It would be even better to set the overall max disk space that can be
used from one "docker run" call, but this is currently not supported for
ext4: https://github.com/moby/moby/issues/29364

Related: OS#6704
Change-Id: I4f9d5ad33c2d6e003d239e8b2c97753d64dd00f6

jobs: manually trigger "git gc" for linux.git

We already use shallow clones for linux.git, and git runs a garbage
collector automatically to ensure no longer needed artifacts are
removed. But this did not work anymore on build4 for
build-kernel-net-next, and it increased up to 8.4 GiB:

    8,4 GiB /build-kernel-net-next

After running "git gc" again:

    3,3 GiB /build-kernel-net-next

The reason was that "git gc" did not exit successfully once and wrote a
log file, then refused to run again. Run "git gc --auto" explicitly in
foreground to let abort in such a case, so it does not go unnoticed in
the future.

Change-Id: Ic81ae5a1edb0dbe119e06cc3b49ea69ef81b2a5f

scripts/docker-cleanup: add "docker system prune"

On build4 this freed up another 8.223GB when I just ran it:

  $ docker system prune
  WARNING! This will remove:
    - all stopped containers
    - all networks not used by at least one container
    - all dangling images
    - all dangling build cache

  Are you sure you want to continue? [y/N]

Change-Id: I98aa5324eaf7cf319625d85bc80d431b89ee50a7

ansible/setup-jenkins-slave: add mingw job deps

Support running the legacy job Osmocom-OBS_MinGW_weekly_publish by
installing its dependencies directly in the LXC. This is a workaround
until we modernize the job, see the related issue.

Related: OS#6706
Change-Id: I49ccf5957dda8459a94c48fe5426b16edc7cb3e2

coverity: use proper asn1c branch

Change-Id: I556b0cc038121b9405556f316d71c0fc75f7d177

ansible: update build5-obsworker ssh key

I've reinstalled the build5-obsworker lxc after first upgrading to
openSUSE 15.6 and then discovering that the lxc version is incompatible
with obs-build: 15.6 doesn't have lxc 4 anymore, but a higher version is
not supported by obs-build. I've added a big warning in the wiki so we
don't run into this again until obs-build has been adjusted.

Related: https://github.com/openSUSE/obs-build/issues/1060
Change-Id: I70a4e404fef74694ee851345345924ae95319b3e

ansible/obs-worker: lxc<5: link to upstream issue

Change-Id: Ia1a575a137c7141d49d974e4d6ffb2472abb64bf

scripts/tarballs: add osmo-upf

Change-Id: I934ec64d3c211753fd6c30affd3d7ac9a52ffcda