Add NuGet.config to test projects to fix nuget restore under network isolation#1293
Merged
Add NuGet.config to test projects to fix nuget restore under network isolation#1293
Conversation
…isolation The VerifyImagesWithWebApps tests fail because nuget restore inside test containers cannot reach api.nuget.org due to 1ES Pipeline Template network isolation. Added NuGet.config files pointing to the Azure DevOps public feed to all test project directories that use nuget restore in their Dockerfiles. Co-authored-by: lbussell <36081148+lbussell@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix NuGet restore block due to network isolation
Add NuGet.config to test projects to fix nuget restore under network isolation
Feb 11, 2026
mthalman
approved these changes
Feb 11, 2026
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.
nuget restorein test container builds fails under 1ES Pipeline Template network isolation because there's noNuGet.configin the Docker build context — NuGet falls back toapi.nuget.orgwhich is blocked.NuGet.configpointing to the Azure DevOps public feed (pkgs.dev.azure.com/dnceng/public/...) to all 8 test project directories that runnuget restore:webapp-4.6.2,webapp-4.7,webapp-4.7.1,webapp-4.7.2,webapp-4.8,webapp-4.8.1dotnetapp-4.8,dotnetapp-4.8.1Each Dockerfile already does
COPY . ./, so NuGet picks up the config automatically — no Dockerfile changes needed. Config content matches the repo rootNuGet.config.Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.