[release/3.x] Update tag references to dotnet-buildtools/prereqs (#7608)#7629
Merged
1 commit merged intorelease/3.xfrom Jul 15, 2021
unknown repository
Merged
[release/3.x] Update tag references to dotnet-buildtools/prereqs (#7608)#76291 commit merged intorelease/3.xfrom unknown repository
1 commit merged intorelease/3.xfrom
unknown repository
Conversation
ghost
requested review from
mthalman
approved these changes
Jul 15, 2021
This pull request was closed.
This file contains hidden or 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
1 participant
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.
Description
Description of the change here.
Port #7608 to release/3.x branch as per email sent out
Customer Impact
Customer impact if this change is not made.
release/3.x linux builds will fail. Example failure: https://dev.azure.com/dnceng/public/_build/results?buildId=1240004&view=results
Regression
No
Risk
None, this just moves where we get the docker image from
Workarounds
Are there available workarounds for the bug?
Nope.