Disable packageSourceMapping in NuGet config #15918
Open
+3
−0
Conversation
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
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.
Fixes MSBuild CI issues with restore: link to the failed CI run.
Error message
Investigation:
Fixing a malformed NuGet configuration in the msbuild repository (dotnet/dotnet#550) enables the use of package source mappings for MSBuild repo, including the bits that flow to MSBuild from arcade. There is a NuGet configuration in arcade that clears the
packageSourcessection without clearing the correspondingpackageSourceMapping, leaving the feature on. Absence of the wild cards fordotnet-core-internal-toolingthen causes errors in the MSBuild CI.Changes:
This PR clears the
packageSourceMappingdisabling the feature for this NuGet config.Note: Alternatively, we can add the wild card for
dotnet-core-internal-tooling.