This repository has been archived by the owner on Dec 7, 2023. It is now read-only.
Add kernel image release workflow #722
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
darkowlzz
requested review from
chanwit,
luxas,
stealthybox and
twelho
as code owners
This adds a new workflow for building and releasing kernel images. It builds different versions of kernels in different jobs. Different kernel arch are build in the same job and pushed together to the container registry. Once pushed, the manifest list is also updated for the pushed images.
stealthybox
force-pushed
the
kernel-image-release
branch
from
09c9df4
to
56688dc
Compare
stealthybox
force-pushed
the
kernel-image-release
branch
from
56688dc
to
6cdf713
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This adds a new workflow for building and releasing kernel images.
It builds different versions of kernels in different jobs. Different
kernel arch are build in the same job and pushed together to the
container registry. Once pushed, the manifest list is also updated for
the pushed images.
Tested this on a fork https://github.com/darkowlzz/ignite/runs/1315667990?check_suite_focus=true. Took about an hour to build everything and publish.
The images were pushed to https://github.com/users/darkowlzz/packages/container/package/ignite-kernel
Manually tested the kernel image with a VM to ensure it works.