mirror of
https://git.proxmox.com/git/mirror_zfs.git
synced 2025-06-28 12:07:40 +03:00
![]() Add a new 'zfs-qemu-packages' GH workflow for manually building RPMs and test installing ZFS RPMs from a yum repo. The workflow has a dropdown menu in the Github runners tab with two options: Build RPMs - Build release RPMs and tarballs and put them into an artifact ZIP file. The directory structure used in the ZIP file mirrors the ZFS yum repo. Test repo - Test install the ZFS RPMs from the ZFS repo. On Almalinux, this will do a DKMS and KMOD test install from both the regular and testing repos. On Fedora, it will do a DKMS install from the regular repo. All test install results will be displayed in the Github runner Summary page. Note that the workflow provides an optional text box where you can specify the full URL to an alternate repo. If left blank, it will install from the default repo from the zfs-release RPM. Most developers will never need to use this workflow. It is intended to be used by the ZFS admins for building and testing releases. This commit also modularizes many of the runner scripts so they can be used by both the zfs-qemu and zfs-qemu-packages workflows. Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Reviewed-by: Tino Reichardt <milky-zfs@mcmilk.de> Signed-off-by: Tony Hutter <hutter2@llnl.gov> Closes #17005 |
||
---|---|---|
.. | ||
generate-ci-type.py | ||
merge_summary.awk | ||
qemu-1-setup.sh | ||
qemu-2-start.sh | ||
qemu-3-deps-vm.sh | ||
qemu-3-deps.sh | ||
qemu-4-build-vm.sh | ||
qemu-4-build.sh | ||
qemu-5-setup.sh | ||
qemu-6-tests.sh | ||
qemu-7-prepare.sh | ||
qemu-8-summary.sh | ||
qemu-9-summary-page.sh | ||
qemu-prepare-for-build.sh | ||
qemu-test-repo-vm.sh | ||
qemu-wait-for-vm.sh | ||
README.md | ||
replace-dupes-with-symlinks.sh |
Workflow for each operating system:
- install qemu on the github runner
- download current cloud image of operating system
- start and init that image via cloud-init
- install dependencies and poweroff system
- start system and build openzfs and then poweroff again
- clone build system and start 2 instances of it
- run functional testings and complete in around 3h
- when tests are done, do some logfile preparing
- show detailed results for each system
- in the end, generate the job summary
/TR 14.09.2024