publish-tarballs: ignore some libosmo-sccp-legacy (details)
Commit
8ba48eb28a7b0631dd4f3539c815ffb7d80de122
by laforge
repo-install-test: fix ca-certificates-java error
The repo-install-test started to fail on debian 10 with the following error. Apparently this happens when installing ca-certificates-java after installing java. Add a workaround.
Setting up ca-certificates-java (20190405) ... head: cannot open '/etc/ssl/certs/java/cacerts' for reading: No such file or directory Exception in thread "main" java.lang.InternalError: Error loading java.security file
Commit
a9e9c366b1bcf93acc92cc56dff0dacae8307ed6
by laforge
repo-install-test: ignore limesuite-images
Don't attempt to install limesuite-images. It runs a post-install script that downloads files from an external server and fails currently, as there are no images for 23.10. While we have limesuite-images packages in our OBS repository, this is just a side-effect of building limesuite. What we are really interested in is liblimesuite for osmo-trx, as I understand.
Add --no-install-recommends to the apt-get install line in install_repo_packages_debian, because the main limesuite package has limesuite-images in recommends and would pull it in otherwise.
Commit
0c79a15162b067822f561259e8b35fafbac286ac
by Oliver Smith
tarballs: git archive: put files in directory
Make the releases created from the "git archive" code path more similar to the autotools releases, by having all files in a subdirectory with the project name and tag name instead of having them directly in the root of the tarball.
Commit
38707a473cea49f39c815ac8bab1864dc11cd9dc
by Oliver Smith
tarballs: git archive: make proper tar.bz2
Compress the tarball from "git archive" with bzip2 to turn it into a proper .tar.bz2. Previously the archive was named .tar.bz2, but it was just a regular tarball as git archive didn't guess the type from the filename (supposedly this works for .tar.gz and some others) and just defaulted to tar.
Move the code that adds build_dep.tar.gz to the archive before the bzip2 call, because tar can't add files to the archive if it is compressed.
Commit
0afdbcf8bd96e77bd233b31e2d089a175f89f7ab
by laforge
obs-mirror: keep nightly builds for two years
As we're moving the archive to a machine with sufficient storage, let's extend the time we keep an archive of nightly builds from one month to two years.
+ make -C ../debian-bookworm-build-arm BUILD_ARGS=--pull UPSTREAM_DISTRO=debian:bookworm DISTRO=debian-bookworm IMAGE=osmocom-build/debian-bookworm-build-arm OSMO_TTCN3_BRANCH=master ./scripts/osmo-ci-docker-rebuild.sh: 203: make: not found
Commit
2031b3d747d8d1bb952a6d565aea104a6d1ae315
by Oliver Smith
repo-install-test: update package filtering logic
Instead of filtering with several blacklist_* files that must contain the exact names of packages to be filtered, add a shell function that uses fnmatch for filtering. Combine all lists into one.
This fixes the error we get with each limesuite release, without the need to increase the version in the txt files every time. Currently the repo-install-tests are failing for all debian versions because of this.
Commit
c4ee740d57d283ae76dd1f3ae9497c9e926642a0
by Oliver Smith
jobs: fix undefined parameter log warnings
Adjust all jobs in the gerrit verifications pipeline to use the same parameters from a new include file, to prevent undefined parameter warnings in the log.
Commit
5db0807a64f70e75af8c5e7d2e050930a1062e5e
by Oliver Smith
jobs/gerrit: osmo-upf: don't for build debian 10
osmo-upf currently can't build against debian 10, as the required libnftables-dev version there is too low and we don't provide a backport for it. As discussed, disable it for debian 10.
Adjust CI to build against debian 11 instead (in addition to the usual almalinux 8, debian 12).
Commit
6b136f74d18a243b79fe01cc9ce2f345aae99751
by Oliver Smith
OBS: lib.osc.get_projects: print apiurl
Print the apiurl, to make more obvious what is going on when running the function twice in a row with two different apiurls (as done in the next patch).
Commit
11f9724c3992a0a1c920c5b103cff0a5095c5303
by Oliver Smith
OBS: add jenkins job to check for new distros
Add a new jenkins job to notify us about new versions of Debian, Raspbian and Ubuntu becoming available in the openSUSE OBS. This allows us to consistently follow along and make the repositories available in the Osmocom OBS. I've decided to check the openSUSE OBS instead of checking somewhere upstream, because it takes time between a new release of a distribution and the version becoming available in openSUSE OBS, and we have another job that syncs the configuration with that OBS instance.
Commit
1fc751429621810c78122c418dd8e2fc7db295d7
by Oliver Smith
ansible: fix updating /opt/coverity/current
Remove the previous /opt/coverity/current symlink, before creating the new one. Otherwise the new symlink would be created inside "current" pointing at the old version, instead of replacing "current" with the new symlink.
Commit
a9c93850c35e3bac01b6d58e6c00df0e83806617
by Oliver Smith
jobs/osmo-gsm-tester-virtual: kill old instances
Make sure osmo-gsm-tester gets killed eventually, even if a bug causes it to run forever or if aborted manually.
* add a name to the docker container * kill the docker container if it runs longer than 24h with docker-cleanup.sh * rename fix_permissions_trap to clean_up_trap and kill it there, when it is still running before the job starts and after it is done (in my testing this did not kill it after pressing abort, but it would be killed either at the start of the next job running on the same jenkins node, or after 24h by docker-cleanup.sh)
Commit
33ddf03dfefd3844328b803cbe96bad513b7bc37
by Oliver Smith
OBS: srcpkg Dockerfile: add lsb-release, quilt
Wireshark with Osmocom patches on top of wireshark.git master failed to build. I've reworked the packaging to use the "debian" dir from upstream instead of having our own (now outdated) copy: https://gitea.osmocom.org/osmocom/wireshark/commits/branch/osmith/deb-packaging
Add the additional dependencies that are now required to build the wireshark source package to the Dockerfile.
Commit
61723f812cdfc6cea3d22bc0ef448f9b07dab6ae
by Pau Espin Pedrol
jobs/ttcn: Run ttcn3-epdg-test only under debian12
Test EPDG_Tests.TC_mt_ipv4_echo_req fails when running under debian11 (node build2-deb11build-ansible), most probably due to some kernel bug fixed later on. Since anyway osmo-epdg requires OTP from debian12, it makes no sense to attempt to support older kernel version from debian11, so simply avoid picking debian11 to run the tests.
Commit
467a96c28115352b0af9500f46b58658f6767ad5
by Oliver Smith
jobs/ttcn3: run io_uring tests on specific nodes
io_uring_queue_init fails on some of the jenkins nodes running the TTCN3 testsuites with io_uring. It seems that the kernel is too old on these nodes. Run the testsuites only on jenkins nodes with the new ttcn3-io_uring label, which have a recent kernel.
Commit
cd0de5983124a23bb8c8f85651a8a1bfba317a6b
by Oliver Smith
jobs/gerrit: libosmocore: run on io_uring nodes
We have at least one node where the io_uring backend does not work. Allow running the osmo_io tests with the io_uring backend in CI by limiting the jenkins nodes used to the ones where we know that io_uring works.
Commit
c1fe54aaf884549a3831b83848fb3cf8c5d24bbf
by Oliver Smith
jobs: add osmocom-obs-ewild
Similar to osmocom-obs-nhofmeyr, add a jenkins job that automatically picks up changes in Hoernchen/mssdr branches in the Osmocom projects, and builds binary packages in home:ewild:mssdr.
Commit
afd9d56e0568a61d0b2de010f710baffb71bff25
by Oliver Smith
checkpatch: recognize json_array_foreach etc.
Treat json_array_foreach, json_object_foreach, json_object_foreach_safe etc. the same as if, while, for, switch, and require exactly one space after using it:
Commit
0cc68159f632e4320054290df3baeee517cda71a
by Oliver Smith
jobs/ttcn3: io_uring: set memlock to unlimited
io_uring in the kernel memlocks a big amount of space with older kernels, such as the kernel on host2-deb11build-ansible. It seemed to be enough to increase it to 1 GiB. However now we see it failing again with:
failure during io_uring_queue_init(): Cannot allocate memory Aborted (core dumped)
Set it to unlimited to ensure that a low limit is not the reason we see it failing. If it still happens after this, we probably need to make sure that we don't run too many SUTs with io_uring in parallel on jenkins nodes with older kernels.
Commit
ec9efbf6494a1bad8a16f0c5b33f878a62822500
by Oliver Smith
repo-install-test: centos8: fix almalinux keys
Run "dnf upgrade almalinux-release" inside centos8/almalinux8 to upgrade the gpg keys first, in order to prevent gpg key errors while installing packages. We are not running repo-install-test for centos8 in CI anymore (SYS#6759), but I'm currently using this configuration to manually test that fixing permissions during upgrade and running systemd services as users works as expected on an rpm-based system.
Commit
b2e128511d5aeae1eb27a7465197012fac643da2
by Oliver Smith
OBS: move gerrit-binpkgs logic to separate script
As I'm preparing slides for a OsmoDevCon talk, I'm realizing that it is quite cumbersome for users to build debian packages from Osmocom git repositories (the same way gerrit does it, to reproduce errors locally).
Move the logic from the gerrit-binpkgs job to a separate script that can be run from an Osmocom git repository, will figure out the repository name from there and only needs the target distribution as argument.
Usage example: $ git clone https://gitea.osmocom.org/osmocom/osmo-ci $ cd libosmocore $ ../osmo-ci/scripts/obs/gerrit_binpkgs.sh debian:12 # or debian:11, debian:10, almalinux:8
Commit
ef2d95d0a298da20043e3ec37f343c6661eedb01
by Oliver Smith
ttcn3-bsc-test-io_uring: limit jenkins nodes again
Run this job only on jenkins nodes with a linux kernel of 6.1.x or higher. The io_uring implementation consumes a lot more memory on e.g. the 5.10.x kernel of host2, which causes osmo-bsc to run out of memory in other places:
<0002> system_information.c:1641 bts 0: Error while generating SI4: Cannot allocate memory (-12) <0002> bts_trx.c:505 Cannot generate SI4 for BTS 0: error <Cannot allocate memory>, most likely a problem with neighbor cell list generation
Commit
0aa60b04a5193fc3d79ce64c9ce94ebed42a96bb
by Oliver Smith
ansible/setup-jenkins: install rsync
After recent refactoring of the gerrit-binpkgs job, rsync is now requried on the jenkins nodes. It was installed on the ones where I tested, but not on all of them.
Fixes: b2e12851 ("OBS: move gerrit-binpkgs logic to separate script") Change-Id: Ic8ffd61fc2c89574085e9c3abbceb554f3c5da6a
Commit
91a79bd8aa8e7901a7d687b6222df360db1bcdc5
by Oliver Smith
jobs: gerrit: build osmo-pcap + dep for centos7
We are about to remove the rpm spec files for almost all Osmocom git repositories. The only two git repositories where we still need them, because we have a customer using them on centos 7, are libosmocore and osmo-pcap (SYS#6760). Add CI to ensure that these still build fine, and that we don't remove these by mistake.
Commit
902fb23413dbb3795dce7a39d86e854f4144d31f
by Oliver Smith
OBS: gerrit_binpkgs: use --no-meta
Don't let packages built with gerrit_binpkgs.sh depend on an osmocom-master meta package. This makes it easier to install and test the built packages locally.
Commit
d974243ef9bf4d2f7374dd98d4c9c525cad12cda
by Oliver Smith
jobs/ttcn3: run ttcn3-msc-test earlier
It seems like various tests are failing from time to time due to the builder having a too high load. As several ttcn3 testsuites run around 4 am already, move ttcn3-msc-test to 1 hour earlier where we don't have anything currently.
osmo-bts in theory can also benefit from io_uring, at least because it can maintain multiple RTP connections for voice calls. Let's execute the respective testsuite with io_uring too.
Commit
3bd97cc86a24f4ad34864fd38c21c6f8e6ba58f8
by Oliver Smith
jobs/ttcn3: update ttcn3-ggsn-test-kernel
Remove ttcn3-ggsn-test-kernel-pablo-gtp, as the IPv6 GTP patches have been merged. Add ttcn3-ggsn-test-kernel-net-next and ttcn3-ggsn-test-kernel-torvalds instead, which run the master/nightly version of osmo-ggsn against HEAD of the kernel trees in netdev/net-next and torvalds/linux.
Commit
3b10b6c6d295801aca78ee2a3c05ffb10c8891c4
by Oliver Smith
OBS: add update_obs_eclipse_titan.sh
Add a script to easily update the eclipse-titan package from a git repository. This replaces the previous workflow of downloading the previous source package, modifying it, and re-uploading it. With the git repository, it is easier to see which patches are included, and it is easier to modify the packaging (e.g. add new patches to fix build with latest gcc), and easier to upgrade the eclipse-titan version.
I've done this change because it failed to build with the most recent GCC in Debian Unstable. Backporting Vadim's patch from upstream fixes it.
Commit
e6d4b42cea8c54b5b20637262a16ed8abf06102f
by laforge
jenkins-jobs-osmo: new file
Do not recommend to the user anymore to put the Osmocom jenkins server in their global jenkins-job-builder config, as this may lead to jobs from other repositories being deployed to the Osmocom jenkins by accident.
Instead of that, let the user put the config in this path: ~/.config/jenkins_jobs/jenkins_jobs_osmo-ci.ini
Add a wrapper script that users this path, and makes sure that no global config is present.
Commit
0674a258c1c5726d7cd05e1e38990487800859ea
by Oliver Smith
ansible/setup-jenkins: add more utils
* etckeeper: to automatically have /etc changes versioned in git; we already use it in various other places * ncdu: to figure out what consumes space * tree: list directory trees, useful to quickly check if e.g. ccache and jenkins workspace dirs are populated properly
Commit
b8c6a5024658f0a1ad628b1ab319a483d7c55ef5
by Oliver Smith
OBS: fix python 3.12 compat
Fix for:
File "/home/user/code/osmo-dev/src/osmo-ci/scripts/obs/lib/__init__.py", line 112, in check_required_programs if not importlib.find_loader(module): ^^^^^^^^^^^^^^^^^^^^^ AttributeError: module 'importlib' has no attribute 'find_loader
Commit
67a5fc886a176ae9485400e3e957ab728a9007d3
by Oliver Smith
jobs: add osmocom-obs-nightly-asan
Add a new job that builds source packages for osmocom:nightly:asan, and uploads them there.
It was considered whether we should instead of building a binary repository with asan packages in OBS, just build all packages and libraries from source at the jenkins builders. We decided against it, see the related discussion.
Commit
3b20d2a281430c44e2f2bb95109708aa85eeff99
by Oliver Smith
OBS: get_git_version: debian/changelog as fallback
Fix osmocom-bb getting 0.1.0 as version:
osmocom-bb: has no git tags, using 0.0.0 as version osmocom-bb: building source package 0.0.0.3621-d70e osmocom-bb: WARNING: version from changelog (0.1.0) is higher than version based on git tag (0.0.0.3621-d70e), using version from changelog (git tag not pushed yet?)
With this patch:
osmocom-bb: has no git tags osmocom-bb: getting version from debian/changelog osmocom-bb: building source package 0.1.0.3621-d70e osmocom-bb: adding debian/changelog entry (0.1.0 => 0.1.0.3621-d70e)
Commit
6a2451a0ad3dd2f5e3179d64446d9d553a37016d
by Oliver Smith
jobs/coverity: adjust mount path to new home dir
With the related docker-playground patch, the home dir for the build user has actually been changed from /home/build to /build. This doesn't matter for all other jobs it seems, but the coverity job here fails because it tries to access $HOME/osmo-ci/coverity.
Adjust the mount path, so it works again as expected.
Fix for: ./jenkins.sh: line 37: /build/osmo-ci/coverity/get_token.sh: No such file or directory
Commit
afae3d79b5656fa24a4eeb6208e8f2ca379967b4
by Oliver Smith
jobs/coverity: fix clean up permission errors
Don't mount the host's osmo-ci/coverity dir in /build/osmo-ci/coverity. The current working dir is mounted as /build, and because docker creates the /build/osmo-ci directory structure as root, we end up with having subdirectories created by root in our current working dir. These then cause an error on the next run when jenkins tries to clean them up.
Fixes: 6a2451a0 ("jobs/coverity: adjust mount path to new home dir") Change-Id: Ie0aa02d3821df6d0505748a7dd70ff67e4cf1405
Commit
637e5c1a89beb6353b7a6aff6b409037d73ad2c6
by Oliver Smith
CI: OBS: centos7: use vault.centos.org
The centos7 images try to use mirrorlist.centos.org to determine the fastest mirror, and then download binary packages from there. But mirrorlist.centos.org isn't online anymore. Use the vault instead.
Without this patch, the mirrors that can't be reached are ignored, and later on it fails to properly install packages because of missing dependencies.
Commit
0014a5c1c18e057b037a479cb19df90cf22581ad
by Oliver Smith
gerrit-verifications-dahdi: set concurrent: false
Each of the gerrit-dahdi-linux-* jobs has a 3-4 GiB workspace directory with a full linux tree. We keep them on disk so we don't need to clone the linux tree with each build.
This makes sense, but set concurrent to false to not create more of these than necessary. These directories stood out when investigating why build4 was running out of space.
Commit
dc413b56dfebcd9acd66761103783ee9c82b0158
by Oliver Smith
jobs/osmocom-build-tags…: fix workspace clean
As this job tries to archive the build logs after running, don't remove the entire workspace. Instead remove the paths that take up the most space, which are the one with the git clones and build artifacts (_deps) as well as the one with the temporary installation dirs (_temp/_inst*).
Fixes: b20e8e8b ("jobs/various: clean workspace on success") Change-Id: Ied86ba80b38a9b10a7a96631e6dedee9f3762c3b
Commit
3633d1f62e9615549a7fd32056f6b544825019dd
by Oliver Smith
jobs/update-osmo-…: only trigger container rebuild
Installing osmo-python-tests to the jenkins nodes should not be needed anymore, as builds of almost all jenkins jobs are done in docker where we install osmo-python-tests inside the containers where it is needed. We already removed the initial deployment to jenkins nodes via ansible in I7c87bd516d1bcdbcc21f65909dabbd3ccc38eede ("ansible: osmocom_build_deps: remove"), let's adjust the job that updates osmo-python-tests too. Instead of deploying it directly, only trigger a rebuild of containers.
I'm doing this now because the jenkins job started failing after I42ba71e2fd0ceb8466758ea46e9ae33e3d4fcb91 ("contrib/jenkins.sh: use virtualenv and pip") on some nodes where virtualenv is not available. The contrib/jenkins.sh script was used for both CI verification and to actually deploy this python package to the jenkins nodes, which was not really obvious and also as noted above isn't needed anymore.
Commit
d854bf573923aebafb3125bc021cb8914c2f6237
by Oliver Smith
OBS: osmocom:master: ignore missing commit_*.txt
Do not abort if the commit_*.txt file has been deleted from a package in osmocom:master. Instead, assume the package is outdated, create a new source package (with commit_*.txt) and replace the existing source package.
This is useful to force rebuilding a package, e.g. if the previous source package was built when the git tag was not pushed yet, and therefore the version in the package and for libraries, in the pkg-config data, don't have the proper version yet.
Commit
85359ba81d4f39fa6367659552a506a9a9f411dd
by Oliver Smith
OBS: replace - with . in version for d/changelog
Fix for: dpkg-buildpackage: info: source version 2:0.1.2-osmo-epdg ... dpkg-source: error: can't build with source format '3.0 (native)': native package version may not have a revision
Commit
9b36d2a8163d7b880c5d0f7ab888d91d6c4ac06b
by Oliver Smith
OBS: fix up-to-date check for strongswan-epdg
Move the code to transform the version from the git tag to the version that we can use in debian/changelog to a separate function. Use it not only when generating the version for debian/changelog, but also when checking if the current git tag is up-to-date.
Without this patch, it always considers strongswan-epdg outdated: strongswan-epdg: building source package (outdated: osmo-epdg-0.1.2 <=> 0.1.2.osmo.epdg in OBS)
Commit
0441e6d88b48bfd0d025044b2f154ee4e0cc57ba
by Oliver Smith
OBS: latest: handle "version is None"
Fix the Osmocom_OBS_latest job, which currently fails on git repositories where no tagged release can be found with:
File "/obs/lib/debian.py", line 96, in transform_version if "osmo-epdg-" in version: ^^^^^^^^^^^^^^^^^^^^^^^ TypeError: argument of type 'NoneType' is not iterable
Fixes: 9b36d2a8 ("OBS: fix up-to-date check for strongswan-epdg") Change-Id: I69cb884d499d1f6a8cae4b4585d31b5bc095fd6e
Commit
9f2b10968915cca7b7e44b1834321908b18a58b3
by Vadim Yanitskiy
OBS: add tag_pattern(), make tag patterns stricter
* add a convenience helper to avoid regexp body duplication * r'[0-9]*' is not strict enough, we want one or more digits * replace r'[0-9]' with r'\d' to make statements a bit shorter
Commit
8dd8e811961771bcf81066c5baba1fe36b856b32
by Oliver Smith
registry-rebuild-upload-testenv: new job
Add a job that updates the one podman image used by ttcn3 testsuites with testenv to the registry. The new testsuite jobs will not build their own images anymore, just pull this one at the start.
Commit
3700f45f4d49903a12820761c7e47d06489df118
by Oliver Smith
jobs/ttcn3-testsuites-testenv: initial
Move the first testsuites over from the old docker-playground based architecture of running testsuites to testenv. I'm doing this iteratively to avoid regressions.
Commit
5b75d6be44107b02b9ea7057239f1a3aee0361ce
by Oliver Smith
jobs/osmocom-depcheck: disable mail notifications
This is a manually triggered job that users may use if they want to verify minimal versions of dependencies mentioned in configure.ac result in a successful build. Don't notify the mailing list about it.
Commit
8fe1efa6d4441e655d477e8e5837592e0d6d910c
by Oliver Smith
ansible: podman: use fuse-overlayfs
The default driver "vfs" leads to container crashes on heavy i/o load on our jenkins machines. Use "fuse-overlayfs" instead, which does not have these problems.
Add a systemd service that creates /dev/fuse when the LXC container starts and configure the driver via ~/.config/containers/storage.conf.
Note: when changing the storage driver, the previous storage database needs to be removed (~/.local/share/containers/storage/). I've done this manually before rolling out this change.
Commit
c98cd9bcee9677db08817d74fffca01be1c3c641
by Oliver Smith
jobs/ttcn3-testsuites-testenv: add s1gw
Remove the docker-playground based job and add a new testenv based job instead. Add one for -latest too as we recently tagged the first releases.
Do not limit the job to a specific node, looks like this was pasted from the above job by mistake. I've successfully ran this on another node build2-deb11build-ansible.
Commit
cabaaa9e7a4455cb9763eba303f9ec3680f28a35
by laforge
jobs/{gerrit,master,update-osmo-ci}: add aarch64 case
The newly set up rpi4-raspbian11build-ansible-1 returns aarch64 for arch (it has an aarch64 OS instead of 32-bit arm like the others currently have). Add "aarch64" to the cases next to arm*, so these work as expected again.
Commit
914b58cb79f85a3956b7c38fc51b143864a331e6
by laforge
jobs/{master,gerrit}: rpi4-raspbian11 -> raspbian
Rename the jenkins label rpi4-raspbian11 to raspbian so the name is not misleading with how we currently use it. One raspberry pi has been reinstalled with raspbian12 (OS#6549) and we also use it for LX2 with a raspbian container (OS#5873, therefore remove rpi4 from the name).
The OS running directly on the rpi / in the LXC is not that important anyway since we run the actual jobs in docker with the latest debian version (currently 12).
Commit
c0fd46590420d57636a381c8b113a1fb8d1ecd40
by laforge
jobs/{gerrit,master}: aarch64: use setarch linux32
Pretend to be a 32 bit arm machine when running the arm jobs, so in combination with the related commit we can build test for 32 bit arm on rpi4s with a 64 bit raspberry pi OS.
Commit
3a26fd299b052858a64d6243492a95c76e940a97
by laforge
Stop building openbsc
With recent changes in libosmo-sccp, openbsc does not build anymore. The openbsc.git repo has been unmaintained/unsupported for 7 years, so let's finally remove related build jobs instead of fixing this.
Commit
b2e064a44ebf59bdacf4bc5d8ac890625ce6cb4f
by Oliver Smith
jobs/osmo-gsm-tester-build: fix Missing parameter
Use OSMO_GSM_TESTER_BRANCH as shell variable ('$...'), not as jenkins job builder parameter (${...}). This is how we do it in other jobs as well, e.g. jobs/osmocom-obs.yml.
Apparently the workaround in the file happened to work earlier, but it does not work anymore with Jenkins Job Builder version 6.3.0. Remove it.
Commit
2410e86b2a832f1345445f700df1a665f9394397
by Oliver Smith
libosmo-sccp -> libosmo-sigtran
Adjust to: * libosmo-sccp.git has been renamed to libosmo-sigtran.git * libosmo-sccp static libraries have been split into libosmo-sccp-legacy.git
build-old-tags-against-master: libosmo-sccp is intentionally kept in REPOS_TAGS, so old libosmo-sccp versions are built against current master of Osmocom libraries.
![[Jenkins]](/jenkins/static/62d04a6b/images/svgs/logo.svg){kind=logo}
