Skip to content

Add FileExtensionSignInfo for .cab to fix unsigned cab files inside ANCM MSIs#66443

Merged
wtgodbe merged 2 commits into
dotnet:mainfrom
jesuszarate:dev/jezarat/sign-cab-files
May 22, 2026
Merged

Add FileExtensionSignInfo for .cab to fix unsigned cab files inside ANCM MSIs#66443
wtgodbe merged 2 commits into
dotnet:mainfrom
jesuszarate:dev/jezarat/sign-cab-files

Merge branch 'main' into dev/jezarat/sign-cab-files

9f47016
Select commit
Loading
Failed to load commit list.
Build Analysis / Helix Queue Insights (preview) succeeded May 22, 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
aspnetcore-ci 42 minutes, 21 seconds 1 hour, 9 minutes, 28 seconds 1 hour, 36 minutes, 34 seconds
aspnetcore-components-e2e 59 minutes, 55 seconds 1 hour, 5 minutes, 10 seconds 1 hour, 10 minutes, 25 seconds

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
osx.15.amd64.open 1 hour, 23 minutes, 36 seconds 0.23% 📈
ubuntu.2404.amd64.open 1 hour, 10 minutes, 35 seconds -0.48% 📉
ubuntu.2204.amd64.open 19 minutes, 57 seconds -0.73% 📉
windows.amd64.vs2026.pre.scout.open 15 minutes, 25 seconds -0.54% 📉

Grafana Dashboard

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

Your Queues

☁️ Helix Queues

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

🏢 On Premises Helix Queues

dotnet/aspnetcore uses the following on-prem queues:

Build Pools

Was this helpful? Yes No