Fix ReleaseConfigs download path after pipeline artifacts migration#16645
Open
mmitche wants to merge 1 commit intodotnet:mainfrom
Open
Fix ReleaseConfigs download path after pipeline artifacts migration#16645mmitche wants to merge 1 commit intodotnet:mainfrom
mmitche wants to merge 1 commit intodotnet:mainfrom
Conversation
The migration from PublishBuildArtifacts to PublishPipelineArtifact (dotnet#16638) changed the download task from DownloadBuildArtifacts@0 to DownloadPipelineArtifact@0, but @0 downloads to by default instead of . The Set Release Configs Vars step then fails because it reads from /ReleaseConfigs/ReleaseConfigs.txt. Switch to DownloadPipelineArtifact@2 with an explicit targetPath to /ReleaseConfigs, matching the path the script expects. Fixes: https://dev.azure.com/dnceng/internal/_build/results?buildId=2939506 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Member
Author
|
Unblocks arcade official builds. |
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.
The migration from PublishBuildArtifacts to PublishPipelineArtifact (#16638) changed the download task from
DownloadBuildArtifacts@0toDownloadPipelineArtifact@0, but @0 downloads to$(Pipeline.Workspace)by default instead of$(Build.ArtifactStagingDirectory). The Set Release Configs Vars step then fails because it reads from$(Build.StagingDirectory)/ReleaseConfigs/ReleaseConfigs.txt.Switches to
DownloadPipelineArtifact@2with an explicittargetPathto$(Build.StagingDirectory)/ReleaseConfigs, matching the path the script expects.Fixes: https://dev.azure.com/dnceng/internal/_build/results?buildId=2939506