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.
Related: OS#6163
Change-Id: I0abc49a95197da55f7d83ed4fd1c4ebb6bd14b1e
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).
Change-Id: I789d12ce59ff14f526ab0334e78a6b22a063ec06
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).
Change-Id: I63798d451b66bf728b58b02414c1a44f6156b356
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.
Fixes: OS#6261
Change-Id: Iadc5cd8996eb4ed86634ceb35829a3e9239e598d
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.
Change-Id: I6745b10804685119d68b089f129ec9b0cde8cdf5
The sudo tool is required by the ansible 'become_user' used later in ttcn3-slave.yml
TASK [osmocom-jenkins-slave : ensure jenkins folder exists] *******************************************
fatal: [lx2-raspbian11build-ansible]: FAILED! => {
"changed": false,
"rc": 127
}
MODULE_STDOUT:
/bin/sh: 1: sudo: not found
Related: OS#5873
Change-Id: I2d50ef2dee8e060ff4f84810f2bba62d4801d638
We don't want to install new builders with 15.3, and the playbook
should just detect the installed version rather than making assumptions
Change-Id: I96f9896c0eeab120633d5800198d8b93371f7a5a
We no longer run the archive on the same machine/lxc as the normal
downloads server
Change-Id: Id490690394db9eb773f945ad4d7e65fe7fd5e17a
Related: OS#6257
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.
Change-Id: Ic8529ee5679f15c4e4940a5f095374605c2e5c79
Related: OS#6257
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.
Change-Id: I5830f9123150540a6467c19c64461d2fa1972a52
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.
$ tree osmo_dia2gsup-0.1.1 | head
osmo_dia2gsup-0.1.1
├── build_dep.tar.gz
├── contrib
│ ├── generate_build_dep.sh
│ ├── jenkins.sh
│ └── systemd
│ └── osmo_dia2gsup.service
├── debian
│ ├── changelog
│ ├── compat
Change-Id: If37dcdc04278de0d4479cf72e0ca33c90b7deea8
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.
Change-Id: I237408c805977c831f352a57a301ea45753d1ac1
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
Change-Id: I00b9c97d9d85fb37ba33a48caa732cd50de99683
With the v2.0.0 release of rtl-sdr, it was decided to include the v in
the tag pattern again, so adjust it in the related scripts. Adjust
osmo-fl2k too in the OBS scripts because there the tag pattern was not
set.
Change-Id: If1bb64722bd24b0079d2427ea3b0f5b5c87ef7ac
The previous workaround for building on debian 12 is not needed anymore,
as the related patch has been merged. Replace it with a new workaround
needed for building the limesuite 23.10 release.
Change-Id: I569642ebb13ac3eb3e241642e299be0a0a2ab15d
Now that we run ./configure before building the tarball, make sure the
dependencies are installed.
Related: OS#6227
Change-Id: I82eb0a87f6e294fb258003ebe76f850a99952938
Copy files inside repo-install-test, instead of copying the directory
again. Otherwise it creates a /repo-install-test/repo-install-test/ path
inside qemu and then fails to run the script inside the directory:
Fix for:
sh: 0: cannot open /repo-install-test/run-inside-env.sh: No such file
Fixes: a7791217 ("scripts/repo-install-test: fix sftp compat")
Change-Id: I04d8c0e0fd31ee5d2a0912300dc93f5339bbef11
When running scp, Debian 12 uses the SFTP protocol by default instead of
the legacy SCP protocol. For some reason, this means it doesn't create
the /repo-install-test directory inside QEMU:
+ … scp … -r scripts/repo-install-test root@127.0.0.1:/repo-install-test
Warning: Permanently added '[127.0.0.1]:22793' (ED25519) to the list of known hosts.
scp: realpath /repo-install-test: No such file
scp: upload "/repo-install-test": path canonicalization failed
scp: failed to upload directory scripts/repo-install-test to /repo-install-test
Changing to the legacy protocol with "scp -O" would make it work again,
but instead of doing that add the mkdir so it works with the new
protocol too.
Related: OS#6186
Change-Id: I740affad2ea794094c8faa89a89bcad094e0075d
Fix for:
rsync: [Receiver] change_dir#3 "/downloads/home/releases/web-files/gapk" failed: No such file or directory (2)
Change-Id: I46310d633302028d486dd356147c9c4f35b24940
Make the ansible rule compatible with debian 12. The same package is
already in debian 11 and debian 10.
Fix for:
E: Package 'netcat' has no installation candidate
Change-Id: Idcc90ad7a2a104a9b4f5a76c6c89d74604651530
Add python3-setuptools, as it is needed to run the
update-osmo-python-on-slaves jenkins job.
Add bc, as it is needed in docker-playground.git's network_create() in
jenkins-common.sh.
Related: OS#6186
Change-Id: I1ff0711b7b29ba4dc78f51f257b986d7a0994a96
This is a dummy package that isn't available anymore in debian 12.
https://packages.debian.org/buster/qemu says:
> This package can safely be removed.
We install qemu-user-static and qemu-system-arm, which contain qemu
binaries.
Related: OS#6186
Change-Id: I4d5bd376b1e370d9636b9a2e9e710f5f20b9ae98
Make nc available on jenkins nodes running ttcn3 tests, as it is now
used by ttcn3-hss-test-ogs.
Related: docker-playground Iebeefd9689ae2efa54678b99ff929ca255ec64d1
Change-Id: I397d4fe33813b083b61cdabb1d00ab4ea63a456b
Simulate that we don't have network during package builds in gerrit
verifications, like it is the case when the packages will be built by
OBS.
I've also considered using network namespaces via "unshare -n" or
bubblewrap, but it wouldn't be possible to create a loopback device
inside the network namespace inside docker (maybe with --privileged, but
not worth it) and e.g. the osmo-mgw tests rely on lo.
Depends: osmo-epdg I2bb0b5f608cd5d9a24c2a367425c524447bd002c
Change-Id: I00282552e9988d66fdc269c6230f0e1432ace360
Add the erlang projects found in gerrit-verifications to master-builds
too, as we have it with most other Osmocom projects.
Change-Id: I6cf5a3c1e52ee73ad63eb2d7d5b1af19a9809026
Make it easier to copy entries from gerrit-verifications.yml to
master-builds.yml by using the same url schema in both.
Change-Id: Ibe992dd8027a8b8df8623abc57a590972443449f
Instead of failing when a project has no git-version-gen script, and no
git tags, use 0.0.0 as version. This is needed for the new osmo-epdg
project, which doesn't have tags yet.
Change-Id: I2f0f409feb96611095dfa511a33ea730e5bbf3e4
Adjust srcpkg.py to run a generate_build_dep.sh not only for
osmo_dia2gsup, but for any Osmocom project that has such a script. This
is in preparation for osmo-epdg, which will also have one.
Change-Id: Icd9dc734ec938398668640f77ec83aae4a1ee0f4
Oliver Smith
Daniel Willmann
Harald Welte
Pau Espin