Document CFS NuGet restore workaround for Compute tests - #30091
Open
Haider Agha (haagha) wants to merge 1 commit into
Open
Document CFS NuGet restore workaround for Compute tests#30091Haider Agha (haagha) wants to merge 1 commit into
Haider Agha (haagha) wants to merge 1 commit into
Conversation
Contributor
|
Azure Pipelines: Successfully started running 2 pipeline(s). There may be pipelines that require an authorized user to comment /azp run to run. |
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the Compute test debugging contributor instructions to document a known issue where NuGet restore/build fails on Microsoft-managed developer devices that block direct access to nuget.org, and provides a workaround using a temporary NuGet config with the CFS proxy.
Changes:
- Adds a new Known Issues entry describing NU1301 restore failures when
https://api.nuget.org/v3/index.jsonis inaccessible. - Documents a workaround approach using an out-of-repo NuGet config that replaces
nuget.orgwithhttps://packagefeedproxy.microsoft.io/nuget/v3/index.json.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Comment on lines
+224
to
+226
| - **Root cause**: The repository's `NuGet.Config` explicitly lists nuget.org, which takes precedence over the device's otherwise-unconfigured package-manager default. Device policy blocks direct public-registry access and requires public NuGet packages to be restored through the Central Feed Services (CFS) proxy. | ||
| - **Fix**: Do not modify the repository's `NuGet.Config` and do not request a DIRE solely for this failure. Create a temporary NuGet config outside the repository containing the absolute path to `tools/LocalFeed`, the existing `azure-powershell` Azure Artifacts source, and `https://packagefeedproxy.microsoft.io/nuget/v3/index.json` in place of nuget.org. Restore with `dotnet restore src/Compute/Compute.sln --configfile <temp-config>`, then build with `dotnet build src/Compute/Compute.sln --no-restore`. | ||
| - **Files involved**: NuGet.Config, src/Compute/Compute.sln, the temporary NuGet config outside the repository |
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.
🤖 PR Validation — ️✔️ All clear
Description
Documents the verified workaround for Compute restore failures on Microsoft-managed developer devices where direct access to NuGet.org is blocked.
The new known-issue entry explains why the repository's explicit NuGet.org source bypasses the device's otherwise-unconfigured CFS default and directs developers to use a temporary NuGet configuration outside the repository with the sanctioned CFS proxy. It also preserves the repository configuration and avoids unnecessary DIRE requests.
Validation performed:
https://packagefeedproxy.microsoft.io/nuget/v3/index.jsonreturns a valid NuGet v3 service index.--no-restore.Mandatory Checklist
Please choose the target release of Azure PowerShell.
Check this box to confirm: I have read the Submitting Changes section of
CONTRIBUTING.mdand reviewed the checklist information.No changelog or generated help update is needed because this PR changes contributor troubleshooting instructions only.