Skip to content

[ci] Fix network isolation requirements#11701

Open
dalexsoto wants to merge 4 commits into
mainfrom
dev/alex/networkiso
Open

[ci] Fix network isolation requirements#11701
dalexsoto wants to merge 4 commits into
mainfrom
dev/alex/networkiso

Conversation

@dalexsoto

Copy link
Copy Markdown
Member

No description provided.

Copilot AI review requested due to automatic review settings June 18, 2026 19:23
@dalexsoto dalexsoto requested a review from simonrozsival as a code owner June 18, 2026 19:23

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the Azure Pipelines CI configuration to better comply with network isolation requirements by disabling .NET SDK background network checks and ensuring dotnet tool installs/updates use restricted NuGet feeds rather than api.nuget.org.

Changes:

  • Add DOTNET_CLI_WORKLOAD_UPDATE_NOTIFY_DISABLE and DOTNET_SDK_VULNERABILITY_CHECK_DISABLE to CI variables.
  • Update the shared dotnet-tool install template to use an isolated NuGet.config via --configfile (removing --add-source https://api.nuget.org/v3/index.json).
  • Update the darc tool update step to use PowerShell Core and an isolated NuGet.config via --configfile.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File Description
build-tools/automation/yaml-templates/variables.yaml Adds env vars to disable workload update notifications and SDK vulnerability checks to reduce network egress under isolation.
build-tools/automation/yaml-templates/install-dotnet-tool.yaml Writes and uses an isolated NuGet.config for dotnet tool update to avoid nuget.org access.
build-tools/automation/azure-pipelines.yaml Switches darc AzureCLI script to PowerShell Core and uses a cleared-source NuGet.config for darc tool update.

Comment thread build-tools/automation/yaml-templates/install-dotnet-tool.yaml Outdated
Comment thread build-tools/automation/azure-pipelines.yaml Outdated
Comment thread build-tools/automation/yaml-templates/install-dotnet-tool.yaml Outdated
Comment thread build-tools/automation/azure-pipelines.yaml Outdated
Address review feedback: '--source' clears default feeds and points only at the
required dnceng feed, so we don't need to write a temp NuGet.config and pass
'--configfile'.

- install-dotnet-tool.yaml (apkdiff, dotnet-test-slicer): only 'dotnet-public'
  is needed; both tools live on that mirror.
- azure-pipelines.yaml (microsoft.dotnet.darc): still needs 'dotnet-eng',
  which is the only feed darc is published to.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@jonathanpeppers

Copy link
Copy Markdown
Member

Switched to --source and dropped the temp NuGet.config / --configfile plumbing in both spots:

  • install-dotnet-tool.yamlapkdiff and dotnet-test-slicer are both published to dotnet-public (verified via the dnceng feed), so a single --source pointing at dotnet-public is enough. No need for dotnet-eng or dotnet-tools here.
  • azure-pipelines.yaml (darc step) — microsoft.dotnet.darc is not in dotnet-public; it's only on dotnet-eng, so that one keeps --source set to the dotnet-eng feed.

Pushed as 265fbc5.

jonathanpeppers and others added 2 commits June 18, 2026 16:34
No longer need pscore now that the inline script doesn't write a temp NuGet.config.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants