Split NuGet publishing into ordered buckets with feed-availability gates - #810
Draft
marcpopMSFT with Copilot wants to merge 12 commits into
Draft
Split NuGet publishing into ordered buckets with feed-availability gates#810marcpopMSFT with Copilot wants to merge 12 commits into
marcpopMSFT with Copilot wants to merge 12 commits into
Conversation
…polling Agent-Logs-Url: https://github.com/dotnet/workload-versions/sessions/d59ee713-02c8-46e2-9df1-537b310335df Co-authored-by: marcpopMSFT <12663534+marcpopMSFT@users.noreply.github.com>
Agent-Logs-Url: https://github.com/dotnet/workload-versions/sessions/d59ee713-02c8-46e2-9df1-537b310335df Co-authored-by: marcpopMSFT <12663534+marcpopMSFT@users.noreply.github.com>
Agent-Logs-Url: https://github.com/dotnet/workload-versions/sessions/d59ee713-02c8-46e2-9df1-537b310335df Co-authored-by: marcpopMSFT <12663534+marcpopMSFT@users.noreply.github.com>
Agent-Logs-Url: https://github.com/dotnet/workload-versions/sessions/d59ee713-02c8-46e2-9df1-537b310335df Co-authored-by: marcpopMSFT <12663534+marcpopMSFT@users.noreply.github.com>
Agent-Logs-Url: https://github.com/dotnet/workload-versions/sessions/d59ee713-02c8-46e2-9df1-537b310335df Co-authored-by: marcpopMSFT <12663534+marcpopMSFT@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Split package publishing into separate buckets
Split NuGet publishing into ordered buckets with feed-availability gates
May 11, 2026
Deployment jobs don't automatically checkout source code, so the eng/split-package-publish-buckets.ps1 and eng/wait-for-package-availability.ps1 scripts were not available. Add checkout: self with fetchDepth: 1 to make the scripts accessible during the publish stage. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This reverts commit f3220f2.
1ES release jobs block checkout, so eng/ scripts aren't available on disk in the Publish stage. Copy the two publish scripts into the artifacts/publishScripts directory during the Build stage so they're downloaded alongside the packages in the Publish stage. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
The Arcade template publishes the Artifacts pipeline artifact from Build.ArtifactStagingDirectory, not System.DefaultWorkingDirectory. The source repo is checked out to 'source-branch' subdirectory, and build outputs are gathered to the staging directory before publishing. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…sets Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Member
|
Tested locally publishing to azdo. Will test out with the preview 6 release to nuget. |
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.
Package publishing needed strict ordering to avoid downstream breakage: publish workload packs first, then manifest packages, then the workload set package (
Microsoft.NET.Workloads.*). The pipeline now enforces this order and blocks progression until prior bucket artifacts are discoverable via feed APIs.Publish orchestration in
official.ymlpacksmanifestsworkloadSetPackage bucketing script
eng/split-package-publish-buckets.ps1..nupkgartifacts into:publishBuckets/packspublishBuckets/manifestspublishBuckets/workloadSetFeed availability polling script
eng/wait-for-package-availability.ps1.PackageBaseAddressfor package/version visibility sequentially (one package at a time), matching the desired low-pressure API-check pattern.