-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Set up symlinks for same image artifacts to remove qemu/qemu_uefi_secure #1847
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Need to make the symlink relative for the copying to work. |
Found one more problem, the PXE symlink also needs special treatment for the GitHub Action zip artifact. The old run https://github.com/flatcar/scripts/actions/runs/8599214030?pr=1847 was missing it
FYI: wzip Fixed now:
|
tormath1
reviewed
Apr 9, 2024
tormath1
approved these changes
Apr 9, 2024
The qemu and qemu_uefi_secure images have the same contents as the qemu_uefi image which wastes space on the release server. A similar case is the PXE vmlinuz which is the same as the regular one, too. Set up symlinks for same images, and also detect this when compressing to set up symlinks there as well. To reduce complexity, the qemu and qemu_uefi_secure images are not supported anymore and the Jenkins or GitHub CI will skip over them if specified. Users that build their own images need to adapt, though.
pothos
added a commit
that referenced
this pull request
Apr 9, 2024
Set up symlinks for same image artifacts to remove qemu/qemu_uefi_secure
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The qemu and qemu_uefi_secure images have the same contents as the qemu_uefi image which wastes space on the release server. A similar case is the PXE vmlinuz which is the same as the regular one, too.
Set up symlinks for same images, and also detect this when compressing to set up symlinks there as well. To reduce complexity, the qemu and qemu_uefi_secure images are not supported anymore and the Jenkins or GitHub CI will skip over them if specified. Users that build their own images need to adapt, though.
How to use
Backport
We could also set up symlinks in Origin but it's a bit tricky because the digest files would need to be regenerated for the compressed files.
Testing done
The images on Jenkins look good, the symlinks are in place for both
.img
and.bz2
and the digest files use the respective filenames while the checksum stays the same.The GitHub Actions passed, I've triggered one more run with a change to remove the qemu+qemu_uefi_secure symlinks from the artifacts because the zip archive included the contents again as it can't add symlinks.
changelog/
directory (user-facing change, bug fix, security fix, update)/boot
and/usr
size, packages, list files for any missing binaries, kernel modules, config files, kernel modules, etc.