Repository navigation
Conversation
Add a NativeAOT content-addressed cache and an opt-in Azure Pipelines shadow lane that always executes fresh Helix work items. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: ee547d49-5419-4268-b01f-6b2757f99953
|
Azure Pipelines: Successfully started running 6 pipeline(s). 10 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
Contributor
|
Tagging subscribers to this area: @dotnet/runtime-infrastructure |
This was referenced Oct 20, 2026
agocke
changed the title
Read completed job details to validate the submitted queue alias while preserving the resolved physical queue in provenance. Cover alias resolution, conflicting aliases, and missing-alias fallback. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: ee547d49-5419-4268-b01f-6b2757f99953
Use separate JSON contexts and an explicit command, evaluation, and action pipeline for Helix cache operations. Replace the Python/resources shadow implementation with native shadow orchestration and C# integration tests, organized into sibling source and tests projects. Correct the opt-in gate for the shadow workflow. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: ee547d49-5419-4268-b01f-6b2757f99953
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: ee547d49-5419-4268-b01f-6b2757f99953
Keep shadow validation disabled by default after the enabled CI run. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: ee547d49-5419-4268-b01f-6b2757f99953
Leave the shadow lane enabled while validating cache reuse in the draft PR. The synchronous experimental harness is intentional; disable it before merge. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: ee547d49-5419-4268-b01f-6b2757f99953
This branch has not been 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
1 participant
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.
Summary
Prototype a Linux x64 Helix work-item result cache using a C# NativeAOT executable, with an opt-in Azure Pipelines shadow lane to validate the integration before replacing any executions.
Cache@2pattern: rolling per-build snapshots with stable restore prefixes. Persist completed entries only; recreate input snapshots in each job. The pipeline build ID is not execution-key material.Shadow lane
The new
helixCacheShadowruntime pipeline parameter defaults to false. When enabled in the public project, only the Linux x64CoreCLR_AllSubsetsjob runs the additional validation, after its normal submissions. It uses the existingSystem.Memory.Data.Testsarchive and runtime correlation payload and submits one additional work item toAzureLinux.3.Amd64.Open.The shadow steps are non-gating (
continueOnError); normal tests remain authoritative. The SDK waits for the additional job and cancels it on task cancellation. Evidence is included in the existing build-log artifact underhelix-cache-shadow/.Queue
eng/pipelines/runtime.ymlagainst this branch withhelixCacheShadow: trueto exercise the live path.Draft limitations
Live Azure template expansion, actual submission/collection through this lane, cross-build Azure cache restoration, and unchanged-rebuild hit rates remain to be validated in CI. The cache fingerprints the declared environment, not a worker attestation. ZIPs are currently hashed byte-for-byte, so nondeterministic archive/build output may prevent useful hits. The first shadow lane is public-queue-only; eviction and replacing normal test executions are out of scope.
Note
This implementation and PR description were created with GitHub Copilot.