morgan/systemd
1
0
Fork 0
mirror of https://github.com/morgan9e/systemd synced 2026-04-15 00:47:10 +09:00
Code Issues Packages Projects Releases Wiki Activity
Files
main
systemd/.packit.yml

54 lines
2.0 KiB
YAML
Raw Permalink Normal View History

ci: enable Packit integration Let's enable the Packit integration and see if it's a viable option for us. This configuration builds systemd on Fedora (on x86_64, i386, and aarch64) and runs the unit test suite. To do that, it uses the specfile from Fedora Rawhide[0] with some minor modifications, thus dropping the need to have a specfile in the upstream repository. So far the builds took around 25 minutes each, so speed-wise it's pretty good. The two remaining supported architectures (s390x and armhfp) are excluded, for now, since they're emulated and build there takes a really long time (~4 hours). [0] https://src.fedoraproject.org/rpms/systemd/
2020-03-19 11:37:41 +01:00
---
packit: Simplify configuration
2025-01-06 13:44:03 +01:00
# SPDX-License-Identifier: LGPL-2.1-or-later
ci: enable Packit integration Let's enable the Packit integration and see if it's a viable option for us. This configuration builds systemd on Fedora (on x86_64, i386, and aarch64) and runs the unit test suite. To do that, it uses the specfile from Fedora Rawhide[0] with some minor modifications, thus dropping the need to have a specfile in the upstream repository. So far the builds took around 25 minutes each, so speed-wise it's pretty good. The two remaining supported architectures (s390x and armhfp) are excluded, for now, since they're emulated and build there takes a really long time (~4 hours). [0] https://src.fedoraproject.org/rpms/systemd/
2020-03-19 11:37:41 +01:00
# Docs: https://packit.dev/docs/
specfile_path: .packit_rpm/systemd.spec
packit: drop/replace deprecated directives
2022-12-15 13:14:30 +01:00
files_to_sync:
- .packit.yml
ci: enable Packit integration Let's enable the Packit integration and see if it's a viable option for us. This configuration builds systemd on Fedora (on x86_64, i386, and aarch64) and runs the unit test suite. To do that, it uses the specfile from Fedora Rawhide[0] with some minor modifications, thus dropping the need to have a specfile in the upstream repository. So far the builds took around 25 minutes each, so speed-wise it's pretty good. The two remaining supported architectures (s390x and armhfp) are excluded, for now, since they're emulated and build there takes a really long time (~4 hours). [0] https://src.fedoraproject.org/rpms/systemd/
2020-03-19 11:37:41 +01:00
- src: .packit_rpm/systemd.spec
dest: systemd.spec
# `git describe` returns in systemd's case 'v245-xxx' which breaks RPM version
ci: build the Fedora RPMs with -Werror
2021-01-28 22:27:18 +01:00
# detection (that expects 245-xxxx'). Let's tweak the version string accordingly
ci: enable Packit integration Let's enable the Packit integration and see if it's a viable option for us. This configuration builds systemd on Fedora (on x86_64, i386, and aarch64) and runs the unit test suite. To do that, it uses the specfile from Fedora Rawhide[0] with some minor modifications, thus dropping the need to have a specfile in the upstream repository. So far the builds took around 25 minutes each, so speed-wise it's pretty good. The two remaining supported architectures (s390x and armhfp) are excluded, for now, since they're emulated and build there takes a really long time (~4 hours). [0] https://src.fedoraproject.org/rpms/systemd/
2020-03-19 11:37:41 +01:00
upstream_tag_template: "v{version}"
Packit: build SRPMs in Copr Add srpm_build_deps key to the Packit config to specify needed dependencies for SRPM build and indicate to build SRPM in Copr.
2022-03-09 07:50:29 +01:00
srpm_build_deps: []
ci: enable Packit integration Let's enable the Packit integration and see if it's a viable option for us. This configuration builds systemd on Fedora (on x86_64, i386, and aarch64) and runs the unit test suite. To do that, it uses the specfile from Fedora Rawhide[0] with some minor modifications, thus dropping the need to have a specfile in the upstream repository. So far the builds took around 25 minutes each, so speed-wise it's pretty good. The two remaining supported architectures (s390x and armhfp) are excluded, for now, since they're emulated and build there takes a really long time (~4 hours). [0] https://src.fedoraproject.org/rpms/systemd/
2020-03-19 11:37:41 +01:00
actions:
packit: use the closest matching tag for the checked out revision Packit otherwise tries to get the latest tag by creation date, which doesn't work well in the systemd-stable repo: 2024-01-23 13:40:47.858 upstream.py DEBUG No ref given or is not glob pattern 2024-01-23 13:40:47.859 upstream.py DEBUG We're about to get latest matching tag in the upstream repository /tmp/tmp07g2beo8. 2024-01-23 13:40:47.859 commands.py DEBUG Command: git tag --list --sort=-creatordate 2024-01-23 13:40:47.866 logging.py DEBUG v248.13 2024-01-23 13:40:47.866 logging.py DEBUG v249.17 2024-01-23 13:40:47.866 logging.py DEBUG v250.14 2024-01-23 13:40:47.866 logging.py DEBUG v251.20 2024-01-23 13:40:47.867 logging.py DEBUG v252.21 2024-01-23 13:40:47.867 logging.py DEBUG v253.15 2024-01-23 13:40:47.867 logging.py DEBUG v254.8 2024-01-23 13:40:47.867 logging.py DEBUG v255.2 2024-01-23 13:40:47.868 logging.py DEBUG v255.1 2024-01-23 13:40:47.868 logging.py DEBUG v255 ...
2024-01-23 15:29:08 +01:00
get-current-version:
packit: Switch to meson.version for the current version
2025-02-25 12:01:53 +01:00
- cat meson.version
packit: use the closest matching tag for the checked out revision Packit otherwise tries to get the latest tag by creation date, which doesn't work well in the systemd-stable repo: 2024-01-23 13:40:47.858 upstream.py DEBUG No ref given or is not glob pattern 2024-01-23 13:40:47.859 upstream.py DEBUG We're about to get latest matching tag in the upstream repository /tmp/tmp07g2beo8. 2024-01-23 13:40:47.859 commands.py DEBUG Command: git tag --list --sort=-creatordate 2024-01-23 13:40:47.866 logging.py DEBUG v248.13 2024-01-23 13:40:47.866 logging.py DEBUG v249.17 2024-01-23 13:40:47.866 logging.py DEBUG v250.14 2024-01-23 13:40:47.866 logging.py DEBUG v251.20 2024-01-23 13:40:47.867 logging.py DEBUG v252.21 2024-01-23 13:40:47.867 logging.py DEBUG v253.15 2024-01-23 13:40:47.867 logging.py DEBUG v254.8 2024-01-23 13:40:47.867 logging.py DEBUG v255.2 2024-01-23 13:40:47.868 logging.py DEBUG v255.1 2024-01-23 13:40:47.868 logging.py DEBUG v255 ...
2024-01-23 15:29:08 +01:00
ci: enable Packit integration Let's enable the Packit integration and see if it's a viable option for us. This configuration builds systemd on Fedora (on x86_64, i386, and aarch64) and runs the unit test suite. To do that, it uses the specfile from Fedora Rawhide[0] with some minor modifications, thus dropping the need to have a specfile in the upstream repository. So far the builds took around 25 minutes each, so speed-wise it's pretty good. The two remaining supported architectures (s390x and armhfp) are excluded, for now, since they're emulated and build there takes a really long time (~4 hours). [0] https://src.fedoraproject.org/rpms/systemd/
2020-03-19 11:37:41 +01:00
post-upstream-clone:
# Use the Fedora Rawhide specfile
packit: Remove --depth=1 from git clone We need the full history to be able to checkout the right commit afterwards.
2025-03-21 13:34:11 +01:00
- git clone https://src.fedoraproject.org/rpms/systemd .packit_rpm
mkosi: Rework how the pkgenv environment variables are set Instead of including distribution specific files in the subimages, let's have one common mkosi.pkgenv/ directory that handles all the matching which is then included in the subimages. This gives us more control on exactly how we do the matching.
2025-09-01 17:29:54 +02:00
- bash -c 'git -C .packit_rpm checkout "$(grep GIT_COMMIT= mkosi/mkosi.pkgenv/mkosi.conf.d/centos-fedora.conf | cut -d= -f2)"'
packit: Simplify configuration
2025-01-06 13:44:03 +01:00
- bash -c 'echo "%bcond upstream 1" > .packit_rpm/systemd.spec.new'
- bash -c 'echo "%define meson_extra_configure_options --werror" >> .packit_rpm/systemd.spec.new'
- bash -c 'cat .packit_rpm/systemd.spec >> .packit_rpm/systemd.spec.new'
- mv .packit_rpm/systemd.spec.new .packit_rpm/systemd.spec
ci: enable Packit integration Let's enable the Packit integration and see if it's a viable option for us. This configuration builds systemd on Fedora (on x86_64, i386, and aarch64) and runs the unit test suite. To do that, it uses the specfile from Fedora Rawhide[0] with some minor modifications, thus dropping the need to have a specfile in the upstream repository. So far the builds took around 25 minutes each, so speed-wise it's pretty good. The two remaining supported architectures (s390x and armhfp) are excluded, for now, since they're emulated and build there takes a really long time (~4 hours). [0] https://src.fedoraproject.org/rpms/systemd/
2020-03-19 11:37:41 +01:00
jobs:
- job: copr_build
trigger: pull_request
packit: drop/replace deprecated directives
2022-12-15 13:14:30 +01:00
targets:
- fedora-rawhide-aarch64
Revert "ci: temporarily disable Packit's i386" The original issue [0] should be resolved in the current Rawhide. [0] https://bugzilla.redhat.com/show_bug.cgi?id=2237392 This reverts commit 3bf7d7963784669f876fab46e13f71faaf61cb27.
2023-09-17 19:37:45 +02:00
- fedora-rawhide-i386
packit: drop/replace deprecated directives
2022-12-15 13:14:30 +01:00
- fedora-rawhide-ppc64le
- fedora-rawhide-s390x
- fedora-rawhide-x86_64
packit: run tests on Fedora Rawhide via Testing Farm Let's utilize the full power of Packit and run some tests with the just built RPMs. This makes use of the Fedora infrastructure provided by the Testing Farm project [0][1]. With the current configuration, the `tests` job runs tests from the Fedora tests repository [2] in a very similar fashion like Ubuntu CI does, just with different metadata all around it. ATTOW there are only two tests, which are wrappers around unit tests and integration tests; the latter one currently runs only nspawn-based tests, since there's no KVM on the test VMs, and, for now, I'd like to see how well the infra is going to manage our upstream traffic and how stable the whole thing is end up being before increasing the work load. [0] https://docs.testing-farm.io/Testing%20Farm/0.1/index.html [1] https://packit.dev/docs/configuration/upstream/tests [2] https://src.fedoraproject.org/tests/systemd
2023-07-12 10:59:30 +02:00
- job: tests
trigger: pull_request
packit: Load fmf metadata from rpm spec repository Maintaining the fmf metadata and script upstream makes it painful to reuse downstream so let's move the metadata and testing script downstream and load it upstream instead.
2025-03-21 15:13:22 +01:00
fmf_url: https://src.fedoraproject.org/rpms/systemd
# This is automatically updated by tools/fetch-distro.py --update fedora
mkosi: update fedora commit reference to 12f95f807fef5075a8842dd107f83b4c41d5ac26 * 12f95f807f Wrap %autosetup in %_build_in_place check * f9916b6fd1 Revert "Use %autosetup -C" * 044cff4700 Allow empower group * a0acca210d Version 259~rc1 * e455d82fd8 Add various extra explicit Requires * 1a7506a105 Version 258.2 * 256463d690 Restore runlevelX.target units * b17d9c3474 Use %autosetup -C * fe18084a05 Remove hack to stop systemd-networkd-resolve-hook.socket
2025-11-20 15:08:15 +01:00
fmf_ref: 12f95f807fef5075a8842dd107f83b4c41d5ac26
packit: run tests on Fedora Rawhide via Testing Farm Let's utilize the full power of Packit and run some tests with the just built RPMs. This makes use of the Fedora infrastructure provided by the Testing Farm project [0][1]. With the current configuration, the `tests` job runs tests from the Fedora tests repository [2] in a very similar fashion like Ubuntu CI does, just with different metadata all around it. ATTOW there are only two tests, which are wrappers around unit tests and integration tests; the latter one currently runs only nspawn-based tests, since there's no KVM on the test VMs, and, for now, I'd like to see how well the infra is going to manage our upstream traffic and how stable the whole thing is end up being before increasing the work load. [0] https://docs.testing-farm.io/Testing%20Farm/0.1/index.html [1] https://packit.dev/docs/configuration/upstream/tests [2] https://src.fedoraproject.org/tests/systemd
2023-07-12 10:59:30 +02:00
targets:
- fedora-rawhide-x86_64
packit: Load fmf metadata from rpm spec repository Maintaining the fmf metadata and script upstream makes it painful to reuse downstream so let's move the metadata and testing script downstream and load it upstream instead.
2025-03-21 15:13:22 +01:00
# testing-farm in the Fedora repository is explicitly configured to use testing-farm bare metal runners as
# the volume of pull requests there is very low. Upstream the volume of pull requests is much higher and
# we'll bottleneck ourselves if we insist on bare metal runners, so explicitly do not request support for
# nested virtualization so we don't only consider bare metal runners.
tf_extra_params:
environments:
- hardware:
virtualization:
is-supported: false
Reference in New Issue Copy Permalink