Skip to content

Change release pipeline to use push command instead of having outputs #602

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
plnelson merged 1 commit into from
Jul 21, 2026
+11 −15
Merged

Change release pipeline to use push command instead of having outputs #602

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 11 additions & 15 deletions build/yaml/stages/release.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,19 +34,6 @@ stages:
templateContext:
type: releaseJob
isProduction: true
outputs:
- output: nuget
displayName: Push to DevDiv InstrumentationEngine feed
nuGetFeedType: internal
publishVstsFeed: 59c1dfae-dea5-4ea5-ac83-c9abcb4ac339
# 1ES requires every packagesToPush entry to live under packageParentPath, which must be
# an existing folder (no wildcards). $(ArtifactsDirectory) == $(Pipeline.Workspace), the
# root all pipeline-resource artifacts download into.
packageParentPath: $(ArtifactsDirectory)
packagesToPush: $(ArtifactsDirectory)\$(WindowsInstrumentationEngineNuGetArtifactPathPattern);$(ArtifactsDirectory)\$(LinuxInstrumentationEngineNuGetArtifactPathPattern)
allowPackageConflicts: true
publishPackageMetadata: true
verbosityPush: Detailed
strategy:
runOnce:
deploy:
Expand All @@ -67,8 +54,17 @@ stages:

- task: NuGetAuthenticate@1
displayName: NuGet Authenticate
# The 'nuget' output declared in templateContext.outputs pushes the packages here,
# immediately after these deploy steps complete.

- task: NuGetCommand@2
displayName: Push to DevDiv InstrumentationEngine feed
inputs:
command: push
nuGetFeedType: internal
publishVstsFeed: 59c1dfae-dea5-4ea5-ac83-c9abcb4ac339
packagesToPush: $(ArtifactsDirectory)\$(WindowsInstrumentationEngineNuGetArtifactPathPattern);$(ArtifactsDirectory)\$(LinuxInstrumentationEngineNuGetArtifactPathPattern)
allowPackageConflicts: true
publishPackageMetadata: true
verbosityPush: Detailed
on:
# The 'on success' hook runs after the deploy phase (including the NuGet push above)
# has succeeded, so the promote step always runs after the packages are published.
Expand Down
Loading