.github: Add Mu PR Validation workflow#1737
Merged
makubacki merged 1 commit intomicrosoft:release/202511from Apr 8, 2026
Merged
.github: Add Mu PR Validation workflow#1737makubacki merged 1 commit intomicrosoft:release/202511from
makubacki merged 1 commit intomicrosoft:release/202511from
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## release/202511 #1737 +/- ##
=================================================
Coverage ? 2.21%
=================================================
Files ? 1632
Lines ? 419626
Branches ? 4949
=================================================
Hits ? 9308
Misses ? 410243
Partials ? 75
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
os-d
approved these changes
Apr 2, 2026
apop5
approved these changes
Apr 2, 2026
Javagedes
approved these changes
Apr 2, 2026
Member
Author
|
Note: Waiting until all clangpdb-ci.yml changes are in to merge: microsoft/mu_devops#553 |
Adds workflows to run QEMU-based platform validation on pull requests to mu_basecore. This includes: - `mu-pr-validation.yml`: The main workflow that performs the actual QEMU validation, including building and booting. - `mu-pr-validation-pending.yml`: A workflow that posts an immediate "pending" notification on a pull request when it's pushed, indicating that QEMU validation is waiting for CI to complete. This is broken out to its own workflow to use the `pull_request_target` trigger (access to secrets on PRs from public forks) while minimizing the amount of code that runs with those elevated permissions. - `mu-pr-validation-post.yml`: A workflow that posts the results of the QEMU validation run to the pull request once the validation is complete. Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
This was referenced Apr 18, 2026
This file contains hidden or 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
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.
Description
Adds workflows to run QEMU-based platform validation on pull requests to mu_basecore. This includes:
mu-pr-validation.yml: The main workflow that performs the actual QEMU validation, including building and booting.mu-pr-validation-pending.yml: A workflow that posts an immediate "pending" notification on a pull request when it's pushed, indicating that QEMU validation is waiting for CI to complete. This is broken out to its own workflow to use thepull_request_targettrigger (access to secrets on PRs from public forks) while minimizing the amount of code that runs with those elevated permissions.mu-pr-validation-post.yml: A workflow that posts the results of the QEMU validation run to the pull request once the validation is complete.Notes
CLANGPDB Package CIworkflow is a trigger upon its completion.add_mu_pr_val_workflow_e2e_valbranch on mu_devops during this initial rollout period. This allows any necessary adjustments to be made quickly based on observations and feedback.How This Was Tested
Ran the workflow under various conditions on my mu_basecore fork. Some examples of output are shown below.
Note that the "boot times" are not precise. They are the total time for the
--flashonlystep to run including stuart overhead. However, they are not too far off from the boot time and provide the ability to get a relative sense of perf impact.PENDING STATE (when the workflow is waiting for CI to finish)
IN PROGRESS (building / booting QEMU FW with the change)
Granular status updates (see ending text):
BUILD FAILURE
Status check result:
BOOT FAILURE
SUCCESS
Integration Instructions