Skip to content

Commit 946531a

Browse files
committed
Allow PR val build insertion step to be re-run
1 parent 6ad21c4 commit 946531a

File tree

1 file changed

+9
-1
lines changed

1 file changed

+9
-1
lines changed

azure-pipelines-pr-validation.yml

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -159,7 +159,7 @@ extends:
159159
targetType: inline
160160
script: |
161161
$originalBuildNumber = "$(Build.BuildNumber)".Split(' - ')[0]
162-
Write-Host "##vso[task.setvariable variable=OriginalBuildNumber;isreadonly=true]$originalBuildNumber"
162+
Write-Host "##vso[task.setvariable variable=OriginalBuildNumber;isoutput=true;isreadonly=true]$originalBuildNumber"
163163
164164
- powershell: Write-Host "##vso[task.setvariable variable=SourceBranchName;isreadonly=true]$('$(Build.SourceBranch)'.Substring('refs/heads/'.Length))"
165165
displayName: Setting SourceBranchName variable
@@ -326,12 +326,20 @@ extends:
326326
- job: insert
327327
variables:
328328
FancyBuildNumber: $[stageDependencies.build.PRValidationBuild.outputs['FancyBuild.BuildNumber']]
329+
OriginalBuildNumber: $[stageDependencies.build.PRValidationBuild.outputs['FancyBuild.OriginalBuildNumber']]
329330
displayName: Insert to VS
330331
pool:
331332
name: VSEngSS-MicroBuild2022-1ES
332333
steps:
333334
- download: current
334335
artifact: VSSetup
336+
337+
# RIT looks at the build number and cannot handle the fancy build version.
338+
# While in normal scenarios this is already set to the original number, we reset it again here in case this is a re-run.
339+
- powershell: Write-Host "##vso[build.updatebuildnumber]$(OriginalBuildNumber)"
340+
displayName: Reset BuildNumber
341+
condition: succeeded()
342+
335343
- powershell: |
336344
$branchName = "$(Build.SourceBranch)".Substring("refs/heads/".Length)
337345
Write-Host "##vso[task.setvariable variable=ComponentBranchName]$branchName"

0 commit comments

Comments
 (0)