Skip to content

Restore with command: custom so nuget.config is not rewritten #792

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
wangbill (YunchuWang) merged 1 commit into from
Aug 3, 2026
+9 −4
Merged

Restore with command: custom so nuget.config is not rewritten #792

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 9 additions & 4 deletions eng/templates/build.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,14 +47,19 @@ jobs:
- task: NuGetAuthenticate@1
displayName: Authenticate NuGet feeds

# Restore uses command: custom rather than command: restore. The restore command's
# feedsToUse/nugetConfigPath inputs make the task copy nuget.config into a generated temp
# config and prefix every package source key with "feed-". Package source mapping matches on
# the source key and those entries are not rewritten, so the mapping the Central Feed Service
# requires stops applying and NuGet excludes the only feed. See
# https://github.com/microsoft/azure-pipelines-tasks/issues/15542.
- task: DotNetCoreCLI@2
displayName: Restore
inputs:
command: restore
verbosityRestore: Minimal
command: custom
custom: restore
projects: $(project)
feedsToUse: config
nugetConfigPath: nuget.config
arguments: --configfile nuget.config --verbosity minimal

# Build source directory
- task: DotNetCoreCLI@2
Expand Down
Loading