-
Notifications
You must be signed in to change notification settings - Fork 51
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
Add qemu binary release workflow: #852
Add qemu binary release workflow: #852
Conversation
de83fc4
to
d7d028d
Compare
If you have time to test the TpmReplay feature, instructions are here - https://github.com/microsoft/mu_tiano_platforms/blob/main/Platforms/Docs/Q35/Features/feature_tpm_replay.md. This is a little unique because it uses a TPM emulator. The TPM emulator only works on Linux at the moment. If there is not time to test it, it is used rarely enough, I can take a note to check it later. I recommend at least booting Windows if you haven't done that. |
Agreed. We normally would validate with a Windows boot with the QEMU UEFI. |
Thanks! I will test both. |
Add a new workflow that will build and prepare qemu binaries for both Windows and Linux. This workflow has three triggers: 1. A pull request to the main branch, which will only trigger when either the workflow itself, or the qemu version file is updated. This workflow will upload the binaries as an artifact to the workflow. 2. A release, which will upload the binaries as an artifact to the associated release 3. A manual trigger, which allows for testing the workflow on a custom branch. This will upload the binaries as an artifact to the workflow.
368d5af
to
c54db95
Compare
7f58a15
to
1429b98
Compare
1429b98
to
501d405
Compare
Verified Qemu can boot to Windows for both Windows and Linux qemu binaries. Still need to test the Tpm Replay functionality. |
Verified Tpm Replay works. |
Description
Add a new workflow that will build and prepare qemu binaries for both Windows and Linux. This workflow has three triggers:
A pull request to the main branch, which will only trigger when either the workflow itself, or the qemu version file is updated. This workflow will upload the binaries as an artifact to the workflow.
A release, which will upload the binaries as an artifact to the associated release
A manual trigger, which allows for testing the workflow on a custom branch. This will upload the binaries as an artifact to the workflow.
flow, or firmware?
validation improvement, ...
in build or boot behavior?
a function in a new library class in a pre-existing module, ...
outside direct code modifications (and comments)?
on an a separate Web page, ...
How This Was Tested
A release was performed using this github action on a personal branch (v0.1.9), and was used as an external dependency on a mu_tiano_platforms Draft PR, which is passing, and will be merged once this PR has been merged and a release has been executed.
Integration Instructions
N/A