-
Notifications
You must be signed in to change notification settings - Fork 138
Closed
Labels
area-buildImprovements in source-build's own build processImprovements in source-build's own build processuntriaged
Description
Context
The SB release pipeline is based on the staging pipeline which links to an installer official build that also has an associated VMR build:
Problem
- The official installer build produces SDK
8.0.100-preview.1.23108.10 - The VMR build produces
8.0.100-preview.1.23108.1 - I believe the difference is caused by the build revision where installer had 9 other builds that day, the VMR had its first. But technically, if we got a commit in installer right before midnight the VMR sync might finish after midnight and we could even get
8.0.100-preview.1.23109.1
This problem arises in the SB release pipeline where we're downloading the source-built SDK to upload it to a storage account:
source-build/eng/source-build-release.yml
Line 222 in dcc0541
| patterns: 'dotnet-sdk-$(SdkVersion)-*.tar.gz' |
Question
I am not sure what is the source-built SDK used for and whether this matters?
Metadata
Metadata
Assignees
Labels
area-buildImprovements in source-build's own build processImprovements in source-build's own build processuntriaged