Skip to content

[10.0.4xx] Use dotnetup preview for .NET acquisition - #55640

Open
nagilson wants to merge 4 commits into
dotnet:release/10.0.4xxfrom
nagilson:nagilson/dotnetup-preview-release-10.0.4xx
Open

[10.0.4xx] Use dotnetup preview for .NET acquisition#55640
nagilson wants to merge 4 commits into
dotnet:release/10.0.4xxfrom
nagilson:nagilson/dotnetup-preview-release-10.0.4xx

Merge branch 'release/10.0.4xx' into nagilson/dotnetup-preview-releas…

7ff1222
Select commit
Loading
Failed to load commit list.
Build Analysis / Helix Queue Insights (preview) succeeded Aug 6, 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 31 minutes, 52 seconds 1 hour, 15 minutes, 45 seconds 1 hour, 59 minutes, 38 seconds

😕 dotnet/sdk doesn't use any Helix Queues.

This GitHub check is meant to show insights into the status of Helix as configured for this Repository.

We couldn't find any queues that this repository uses. If this seems wrong, please ensure that your pipeline is configured under dnceng's AzDo orginization under the public project. Please contact @dnceng for more assistance.

Grafana Dashboard

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

Build Pools

Was this helpful? Yes No