Add Join-Verticals task, use it at the final Join Point #19369
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 |
|---|---|---|---|
| installer | 20 minutes, 19 seconds | 39 minutes, 21 seconds | 58 minutes, 24 seconds |
| installer-source-build | 51 minutes, 31 seconds | 56 minutes, 29 seconds | 1 hour, 1 minute, 27 seconds |
| installer-unified-build | 53 minutes, 45 seconds | 1 hour, 8 minutes, 32 seconds | 1 hour, 23 minutes, 19 seconds |
😕 dotnet/installer 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
Microsoft Hosted
This pipeline will build on the following Microsoft Hosted build pools:
Click here for information about these agents.
- macOS-latest
- macOS-12
Was this helpful?