VMR vs MSFT signing comparison #48404
Draft
Conversation
This file contains 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
dotnet-issue-labeler
bot
added
Area-Infrastructure
untriaged
ellahathaway
force-pushed
the
vmr-msft-signing-comparison
branch
from
b9d84d0 to
4d82a3a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes dotnet/arcade#15192
This PR introduces the following changes:
[dotnet-unified-build-comparison](https://dev.azure.com/dnceng/internal/_build?definitionId=1447&_a=summary)is used for asset and signing comparison. This pipeline runs on every build of main and release branches and can also be run manually.BuildComparerhas been reworked so that there are two sub-commands:assetsandsigning.Test pipeline run