mirror of
https://git.proxmox.com/git/mirror_zfs.git
synced 2025-09-15 21:56:21 +03:00
![]() In the past there have been times when we need to generate new RPMs for an existing ZFS release. Typically this happens when a new RHEL version comes out and the kernel symbols no longer match. To get users to auto-update we just bump the patch number. For example, we had to create zfs-2.1.13-1 for EL8.8 and zfs-2.1.13-2 for EL8.9. This commit adds an optional patch level text box to the github package builder runner. In addition, this commit also uses `hostnamectl` instead of `hostname` for F42+ compatibility, if available. Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Signed-off-by: Tony Hutter <hutter2@llnl.gov> Closes #17638 |
||
---|---|---|
.. | ||
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