Skip to content

Replace branch-mirror-status prompt file with PowerShell script#55111

Open
marcpopMSFT wants to merge 4 commits into
mainfrom
marcpopmsft-fix-branch-mirror-script
Open

Replace branch-mirror-status prompt file with PowerShell script#55111
marcpopMSFT wants to merge 4 commits into
mainfrom
marcpopmsft-fix-branch-mirror-script

Address lbussell review: add doc comments for AzDo resource ID and AP…

888b8e6
Select commit
Loading
Failed to load commit list.
Build Analysis / Helix Queue Insights (preview) succeeded Jul 2, 2026 in 0s

View the current status of Helix

Details

Pipeline Status

The list of queues is cached weekly. If your PR changes what queues your pipelines use, this information will not show the updated queues.

Estimated Pipeline Durations

This model assumes that the current state of the entire CI infrastructure is normal, and that your CI pipelines will succeed.

Pipeline Lower Bound Estimated Time Upper Bound
dotnet-sdk-public-ci 38 minutes, 48 seconds 1 hour, 24 minutes, 8 seconds 2 hours, 9 minutes, 28 seconds
sdk-report-green

Pipelines denoted with ❌ means that this pipeline is highly variable, and we cannot predict its duration. This typically means this pipeline changes the legs it runs based on the PR's changed contents.

Highest Work Item Wait Time Queues

Here's a list of the top 4 queues with the highest work item wait time:

Queue Work Item Wait Time Difference in Moving Avg
windows.amd64.vs2026.pre.scout.open 18 minutes, 46 seconds 0.09% 📈
ubuntu.2204.amd64.open 13 minutes, 16 seconds 0.11% 📈
osx.15.arm64.open 46 seconds -0.63% 📉
osx.15.amd64.open 24 seconds -0.9% 📉

Grafana Dashboard

For more in-depth information on the status of Helix, visit our Grafana Dashboard.

Your Queues

☁️ Helix Queues

dotnet/sdk is currently configured to submit to the following Helix queues:

🏢 On Premises Helix Queues

dotnet/sdk uses the following on-prem queues:

Build Pools

Was this helpful? Yes No