Workaround failing official builds #75898
Merged
10
−0
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
arunchndr
approved these changes
Nov 13, 2024
This was referenced Nov 15, 2024
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.
Related: dotnet/dnceng#4441
Official build run of this PR: https://dev.azure.com/dnceng/internal/_build/results?buildId=2581358&view=results
No idea why, but when the
eng/common/internal/Tools.csprojproject is being restored as part of the "restore internal tools", it works with the arcade-provided NuGet feeds. But when that same project is being restored as part of the "build" step, it reports 401 (Unauthorized) for the visualstudio.com feeds - replacing them with the azure.com equivalents fixes the problem.(Note that technically the second restore of that project as part of the build step is unnecessary, but I didn't find a simple way to disable it.)