mirrors/systemd
0
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2024-11-23 18:23:32 +08:00
Code Issues Packages Projects Releases Wiki Activity
051fddfc41
systemd/.packit.yml

65 lines
2.5 KiB
YAML
Raw 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 18:37:41 +08:00
---
# vi:ts=2 sw=2 et:
#
# Docs: https://packit.dev/docs/
specfile_path: .packit_rpm/systemd.spec
packit: drop/replace deprecated directives
2022-12-15 20:14:30 +08: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 18:37:41 +08:00
- src: .packit_rpm/systemd.spec
dest: systemd.spec
upstream_package_name: systemd
downstream_package_name: systemd
# `git describe` returns in systemd's case 'v245-xxx' which breaks RPM version
ci: build the Fedora RPMs with -Werror
2021-01-29 05:27:18 +08: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 18:37:41 +08: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 14:50:29 +08: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 18:37:41 +08: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 22:29:08 +08:00
get-current-version:
# Show the closest matching tag for the checked out revision, otherwise
# Packit tries to get the latest tag by creation date, which doesn't work
# well in the systemd-stable repo. We also need to sanitize it manually
# since "upstream_tag_template" defined above doesn't apply here.
- "bash -ec 'git describe --tags --abbrev=0 | cut -b 2-'"
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 18:37:41 +08:00
post-upstream-clone:
# Use the Fedora Rawhide specfile
Revert "packit: temporarily use older Rawhide spec" This reverts commit f1adb4a2ea2fd1d54ff8cc17a4d10f2b502cfc69.
2023-07-14 19:48:56 +08:00
- "git clone https://src.fedoraproject.org/rpms/systemd .packit_rpm --depth=1"
packit: drop the 'sources' file after cloning the Fedora repo Otherwise rebase-helper thinks we're are a dist-git repository, replacing the generated git archive with PR changes with the tarball found in the 'sources' file.
2021-04-12 23:56:33 +08:00
# Drop the "sources" file so rebase-helper doesn't think we're a dist-git
- "rm -fv .packit_rpm/sources"
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 18:37:41 +08:00
# Drop backported patches from the specfile, but keep the downstream-only ones
packit: drop unnumbered patches as well
2022-02-17 21:02:04 +08:00
# - Patch(0000-0499): backported patches from upstream
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 18:37:41 +08:00
# - Patch0500-9999: downstream-only patches
packit: drop unnumbered patches as well
2022-02-17 21:02:04 +08:00
- "sed -ri '/^Patch(0[0-4]?[0-9]{0,2})?\\:.+\\.patch/d' .packit_rpm/systemd.spec"
ci: revert back to --werror instead of -Dc_args=-Werror -Dc_args=/-Dcpp_args= don't play well with the RPM hardening macros using $CFLAGS/$CPPFLAGS, since they're mutually exclusive.
2021-03-07 06:17:01 +08:00
# Build the RPM with --werror. Even though --werror doesn't work in all
# cases (see [0]), we can't use -Dc_args=/-Dcpp_args= here because of the
# RPM hardening macros, that use $CFLAGS/$CPPFLAGS (see [1]).
ci: build with -Werror on Fedora Prompted by: https://github.com/systemd/systemd/pull/18400#issuecomment-771602705
2021-02-03 00:02:12 +08:00
#
# [0] https://github.com/mesonbuild/meson/issues/7360
ci: revert back to --werror instead of -Dc_args=-Werror -Dc_args=/-Dcpp_args= don't play well with the RPM hardening macros using $CFLAGS/$CPPFLAGS, since they're mutually exclusive.
2021-03-07 06:17:01 +08:00
# [1] https://github.com/systemd/systemd/pull/18908#issuecomment-792250110
- 'sed -i "/^CONFIGURE_OPTS=(/a--werror" .packit_rpm/systemd.spec'
packit: don't take ownership of /etc/ssh/sshd_config.d/ 7e3607996a creates a symlink under /etc/ssh/sshd_config.d/ and with current Rawhide RPM stuff the systemd RPM tries to take ownership of that directory which conflicts with the openssh-server package. Let's temporarily tweak the regex in split-files.py until this changes makes it to Rawhide.
2023-12-07 16:36:52 +08:00
# Ignore unpackaged standalone binaries
packit: ignore unpackaged files It may take a bit for newly introduced binaries/other files to get properly integrated into the Rawhide specfile, so don't choke up in the meantime when rpmbuild detects unpackaged files.
2022-12-07 20:04:44 +08:00
- "sed -i 's/assert False,.*/pass/' .packit_rpm/split-files.py"
packit: add a libarchive runtime dependency too Addresses https://github.com/systemd/systemd/pull/31075#issuecomment-1911117026: [ 40.039232] testsuite-50.sh[624]: ++ systemd-dissect --make-archive /tmp/tmp.RZEq3t/minimal_0.raw [ 40.044745] testsuite-50.sh[625]: ++ sha256sum [ 40.066693] systemd-dissect[621]: libarchive.so.13 is not installed: libarchive.so.13: cannot open shared object file: No such file or directory [ 40.068577] systemd-dissect[621]: Archive support not available (compiled without libarchive, or libarchive not installed?). [ 40.092242] systemd-dissect[624]: libarchive.so.13 is not installed: libarchive.so.13: cannot open shared object file: No such file or directory [ 40.095716] systemd-dissect[624]: Archive support not available (compiled without libarchive, or libarchive not installed?). [ 40.100510] testsuite-50.sh[538]: + test e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 '!=' '' [ 40.100510] testsuite-50.sh[538]: + test e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 = e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 [ 40.108249] testsuite-50.sh[627]: + tar t [ 40.113791] testsuite-50.sh[626]: + systemd-dissect --make-archive /tmp/tmp.RZEq3t/minimal_0.raw [ 40.120300] testsuite-50.sh[628]: + grep etc/os-release [ 40.176288] systemd-dissect[626]: libarchive.so.13 is not installed: libarchive.so.13: cannot open shared object file: No such file or directory [ 40.180273] systemd-dissect[626]: Archive support not available (compiled without libarchive, or libarchive not installed?). [ 40.184017] testsuite-50.sh[627]: tar: This does not look like a tar archive [ 40.185430] testsuite-50.sh[627]: tar: Exiting with failure status due to previous errors Follow-up for b68f4ca.
2024-01-26 18:08:26 +08:00
# Temporarily add libarchive-devel build dep and libarchive runtime dep
# until the change propagates to Rawhide's specfile
- "sed -ri '0,/^BuildRequires: .+$/s//&\\nBuildRequires: libarchive-devel\\nRequires: libarchive/' .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 18:37:41 +08:00
jobs:
- job: copr_build
trigger: pull_request
packit: drop/replace deprecated directives
2022-12-15 20:14:30 +08: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-18 01:37:45 +08:00
- fedora-rawhide-i386
packit: drop/replace deprecated directives
2022-12-15 20:14:30 +08: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 16:59:30 +08:00
- job: tests
trigger: pull_request
fmf_url: https://src.fedoraproject.org/tests/systemd
fmf_ref: main
tmt_plan: ci
targets:
- fedora-rawhide-x86_64
Reference in New Issue Copy Permalink