What problem does it solve?
Setting up a dotnet repository branch so its official builds register assets in the Build Asset Registry (BAR) and publish packages to a NuGet feed requires coordinating Darc channel associations, Azure Pipelines triggers, and Maestro configuration PRs, which is error-prone when done manually.
Core Features & Use Cases
- Darc Default Channel Setup: Adds a branch-to-channel association via
darc add-default-channel, with fallback authentication using GitHub and Azure DevOps tokens.
- Official Pipeline Trigger Configuration: Edits
azure-pipelines-official.yml so the target branch triggers official builds, both on the branch itself and via a durable PR to the default branch.
- Verification and Error Handling: Verifies the channel association after the Maestro configuration PR merges and handles common failures like HTTP 401s, duplicate associations, and branch name mismatches.
- Use Case: You want experimental branch
demos/my-experiment in dotnet/roslyn to publish its official build packages to the General Testing channel so the team can consume them from a NuGet feed.
Quick Start
Ask the assistant to set up Darc publishing for the dotnet/roslyn branch demos/my-experiment to the General Testing channel.
