From 69e19f7ce3aa03b8f88420f0612776b0ff89c563 Mon Sep 17 00:00:00 2001 From: dotasek Date: Wed, 1 Feb 2023 16:45:41 -0500 Subject: [PATCH] Add artifact publish for copied files --- release-branch-pipeline.yml | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/release-branch-pipeline.yml b/release-branch-pipeline.yml index 135c0958a..83c2c4d3b 100644 --- a/release-branch-pipeline.yml +++ b/release-branch-pipeline.yml @@ -68,6 +68,10 @@ jobs: Contents: "$(System.DefaultWorkingDirectory)/VERSION" TargetFolder: '$(build.artifactstagingdirectory)' displayName: 'Copy Files to: $(build.artifactstagingdirectory)' + - task: PublishBuildArtifacts@1 + displayName: 'Publish Build Artifacts' + inputs: + PathtoPublish: '$(build.artifactstagingdirectory)' - job: get_branch_id timeoutInMinutes: 5 steps: @@ -103,6 +107,12 @@ jobs: Contents: "$(System.DefaultWorkingDirectory)/BRANCH" TargetFolder: '$(build.artifactstagingdirectory)' displayName: Copy the branch name file to the artifact staging directory. + # Publishes the files we've moved into the staging directory, so they can be accessed by the + # release pipeline. + - task: PublishBuildArtifacts@1 + displayName: 'Publish Build Artifacts' + inputs: + PathtoPublish: '$(build.artifactstagingdirectory)' - job: build_and_publish_artifacts # We're going to do a full build, including all unit and intergration tests. We do this here, before any # actual release pipeline kicks off, and we don't do it again at any point in the release pipeline. The assumption here