Separate AzDO and NuGet.org publishing into distinct pipeline stages#802
Open
Copilot wants to merge 2 commits into
Open
Separate AzDO and NuGet.org publishing into distinct pipeline stages#802Copilot wants to merge 2 commits into
Copilot wants to merge 2 commits into
Conversation
Agent-Logs-Url: https://github.com/dotnet/workload-versions/sessions/e432bd1e-2759-4941-adc9-c68990ffbade Co-authored-by: marcpopMSFT <12663534+marcpopMSFT@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Separate publishing to azdo and nuget.org
Separate AzDO and NuGet.org publishing into distinct pipeline stages
May 6, 2026
Member
|
Change looks right. One drawback is that we're downloading the build artifacts in both but I don't think there's a way to avoid that. This would make it so we had two approvals to do but could publish to azdo ahead of time and test before release day. |
There was a problem hiding this comment.
Pull request overview
This PR updates the official pipeline to split package publishing into two separately-approvable stages so operators can validate packages from the AzDO feed before releasing to NuGet.org.
Changes:
- Replaced the single
Publishstage withPublishAzDO(runs whenpublishToAzDO=true) andPublishNuGet(runs whenpublishToNuGet=true). - Ensured the publish order is
Build → PublishAzDO → PublishNuGetwhen both publish flags are enabled, while allowingPublishNuGetto depend directly onBuildwhen AzDO publishing is disabled.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
252
to
256
| - task: 1ES.DownloadPipelineArtifact@1 | ||
| displayName: 🟣 Download build artifacts | ||
| inputs: | ||
| artifactName: Artifacts | ||
| targetPath: $(System.DefaultWorkingDirectory)/artifacts |
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.
Publishing to AzDO and NuGet.org happened in a single
Publishstage with no opportunity to test from the AzDO feed before exposing packages to customers on NuGet.org.Changes
eng/pipelines/official.yml: Replaced the singlePublishstage with two independent stages:PublishAzDO— active whenpublishToAzDO=true, depends onBuildPublishNuGet— active whenpublishToNuGet=true, depends onPublishAzDOwhen both flags are set, otherwise depends directly onBuildEach stage has its own
DotNet-SDK-Workloadsenvironment approval gate, so the two can be approved independently. When both are enabled, the enforced order is Build → PublishAzDO → PublishNuGet, giving operators a window to validate from the AzDO feed before releasing to NuGet.org.