Migrate from PackageES build agents to public Microsoft hosted Azure agents #113
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.
Summary
This PR updates the build pool used for building the MS-ICU Nuget to migrate off the PackageES build agents and uses the public Microsoft hosted Azure DevOps build agents instead.
It also changes the publishing of the symbols for the MS-ICU Nuget, so that we can continue to have symbols available via the public MSDL symbol server.
PR Checklist
Detailed Description
The Package ES build agents are being deprecated, and will stop working after Sept 30th. This means that we need to move off of the
Package ES CodeHub Lab E
pool and find another pool to run our builds on.Originally, I thought that we'd need to migrate to a custom hosted pool (using the 1ES Hosted Pool to run custom agents), but after doing some investigating, it turns out that we can actually run on the public Microsoft hosted Azure DevOps build agents instead.
This means that we don't need to setup and run our own custom pool in an Azure subscription. 😊
Additionally, we can also continue to publish the Windows symbols for the MS-ICU Nuget to the public MSDL symbol server, by making some changes to how things are published.
Instead of using the AAD authentication to publish, we can switch to using a secure variable for a PAT token via the TARGET Dev Bot (@targetdev-bot) in order to publish the symbols. This variable is only accessible to the manually triggered "Release-Nuget" pipeline, so that other pipelines cannot access it.
So the symbols will still be available from the public MSDL symbol server:
https://msdl.microsoft.com/download/symbols