Repository navigation
Use Cake Frosting for parallel desktop CI and artifact validation - #1
Merged
Merged
Conversation
This branch was successfully deployed
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.
The desktop CI workflow previously kept its build/test commands in YAML separately from the local build. Route the existing six offline test runs through a compiled Cake Frosting entry point while retaining their parallel jobs, matrix labels and credential/setup coverage. The package job now also prepares and verifies the five application bundles.
The public publishing workflow, shared desktop/processor validation gate, publication lock, runtime dependencies and library version remain unchanged. The artifact-only target runs no tests and publishes nothing; regression coverage checks its dependency graph so validation reuse can be retained when release preparation is integrated later.
Validation:
The NUnit configuration policy passed. No processor test, public package release or default-branch merge was performed. This draft is ready for review.