Rework the repo to build edk2 release tags #1
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 builder this repo used to pull from has been turned off. It would be nice to have up-to-date edk2 release builds for use with testing in https://github.com/rust-osdev/uefi-rs, without relying on the vagaries of Linux distro releases. Doing our own builds also allows us to ensure we have exactly the build options we want for use with VM testing.
As described in the readme, the intended usage is manually pushing a tag corresponding to a release tag in the edk2 repo. That tag will be built in a container, and the resulting tarball will be pushed as a release in this repo (as long as the release doesn't already exist.)
I've intentionally kept the container build very simple and linear to make it clear what options are being set for each edk2 build. That leads to some duplication there, but I think the end result is quite easy to follow.
Here's an example release from my testing in a fork: https://github.com/nicholasbishop/ovmf-prebuilt/releases/tag/edk2-stable202211-r3