Skip to content

Use Cake Frosting for parallel desktop CI and artifact validation - #1

Merged
oznetmaster merged 1 commit into
masterfrom
codex/cake-ci-integration
Nov 2, 2026
Merged

oznetmaster merged 1 commit into
masterfrom
codex/cake-ci-integration

Conversation

@oznetmaster

@oznetmaster oznetmaster commented Oct 31, 2026 •

Copy link
Copy Markdown
Owner

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:

  • Hosted CI run 41244078546 passed all eight jobs for head 71a0648. Independent download/readback of all seven TRX reports confirmed 1,309 product cases and 19 build-tool cases passed, with no failed or skipped cases. The workflow completed in approximately 2 minutes 25 seconds; this single run is not a controlled speed benchmark.
  • The retained package artifact contains one API-validated NuGet package and five application bundles. Package DLLs match the standalone release DLLs; no Cake runtime dependency was introduced. The artifact-only receipt correctly records that it ran no desktop tests and performed no publication.
  • The original full local pilot passed all 1,309 desktop cases, package/API validation and comparison of all 228 artifact payload entries against a clean reference built by the existing release commands. The CI suite selector and artifact-only entry point also passed locally.

The NUnit configuration policy passed. No processor test, public package release or default-branch merge was performed. This draft is ready for review.

@oznetmaster
oznetmaster merged commit 71a0648 into master Nov 2, 2026
10 checks passed

This branch was successfully deployed

1 active deployment
github-pages — 71a06487 Deployed Nov 2, 2026 by oznetmaster via deploy #51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant