Blob: Add support for 1ES Build Cache, refactor auth #110
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
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.
This change adds support for 1ES Build Cache.
As auth was getting a bit too complicated, I refactored it a bit to be able to just use what is provided instead of requiring the auth type to explicitly be configured.
The TL;DR for 1ES Build Cache is:
$(MSBuildCacheBuildCacheConfigurationFile)$(MSBuildCacheBuildCacheResourceId)For existing scenarios which use the blob account directly, the only real change is you no longer need to set
$(MSBuildCacheCredentialsType).