Skip to content

[CI] Route Unofficial/fork-PR crate downloads through Mxc-Azure-Feed#541

Closed
bbonaby wants to merge 1 commit into
microsoft:mainfrom
bbonaby:user/bbonaby/use-private-feed-for-crates
Closed

[CI] Route Unofficial/fork-PR crate downloads through Mxc-Azure-Feed#541
bbonaby wants to merge 1 commit into
microsoft:mainfrom
bbonaby:user/bbonaby/use-private-feed-for-crates

Conversation

@bbonaby

@bbonaby bbonaby commented Jun 19, 2026

Copy link
Copy Markdown
Collaborator

📖 Description

Updating azure PR builds to use the private feed instead of the public anonymous feed.

Only way for us to see if this is a viable option is try it out. Otherwise we need to add new dependencies to https://dev.azure.com/shine-oss/mxc/_artifacts/feed/MxcDependencies for PRs that update them.

🔗 References

🔍 Validation

✅ Checklist

📋 Issue Type

  • Bug fix
  • Feature
  • Task

GitHub Actions runs the PR validation build automatically. The ADO pipeline
(MXC-PR-Build) is the official build pipeline that signs the binaries; it
runs on merge to main and nightly, and Microsoft reviewers can trigger it
on a PR with /azp run. See docs/pull-requests.md.

Microsoft Reviewers: Open in CodeFlow

Switch Cargo.Setup.Public.yml to append the internal Mxc-Azure-Feed config
(.azure-pipelines/.cargo/config.toml) to the workspace .cargo/config.toml
instead of the public MxcDependencies feed (config.public.toml), to test
whether the private feed removes the dependency on the public feed.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot AI review requested due to automatic review settings June 19, 2026 18:07

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 changes the Azure Pipelines “Unofficial / fork-PR” Cargo setup step to append the internal Mxc-Azure-Feed Cargo registry config (instead of the anonymous public MxcDependencies feed), with the goal of routing crate downloads through the private feed under 1ES network isolation.

Changes:

  • Update the Cargo setup template to append .azure-pipelines/.cargo/config.toml (internal feed) into the workspace .cargo/config.toml.
  • Update the template’s description/display name to refer to Mxc-Azure-Feed rather than the public feed.

Comment on lines +4 to 7
# Appends the internal Mxc-Azure-Feed cargo feed (config.toml) to the
# workspace .cargo/config.toml. Used by Unofficial / fork-PR Rust steps so
# crate downloads work under 1ES pool network isolation (crates.io is not on
# the allowlist). Mirrors the Official setup step in Rust.Build.Steps.Official.yml.
Comment on lines +11 to +12
Add-Content -Path "$(Build.SourcesDirectory)/.cargo/config.toml" -Value ("`n" + (Get-Content -Raw "$(Build.SourcesDirectory)/.azure-pipelines/.cargo/config.toml"))
displayName: Setup Cargo Config (Mxc-Azure-Feed)
@bbonaby

bbonaby commented Jun 19, 2026

Copy link
Copy Markdown
Collaborator Author

/azp run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines successfully started running 1 pipeline(s).

@bbonaby

bbonaby commented Jun 19, 2026

Copy link
Copy Markdown
Collaborator Author

confirmed via the failures that we have to use the public feed

@bbonaby bbonaby closed this Jun 19, 2026
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.

2 participants