dotnet / dotnet/arcade-services

Build Analysis and Helix Queue Insights checks block PRs without AzDO pipelines

Open
#6,587 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
C#
Stars
86
Forks
86
Avg merge
1d 8h
Merged PRs (30d)
35

Description

This PR only has a markdown change and did not kick off an AzDO run. The checks run, but since there's no AzDO build, the checks just sit there in a waiting state. https://github.com/dotnet/runtime/pull/112885 (also see screenshot below)

![Image](https://github.com/user-attachments/assets/d2164eb6-9073-4752-8ce8-f96ff9d0fec0)

Unsure if related, but a change was made to the status of the check recently: https://dnceng.visualstudio.com/internal/_git/dotnet-helix-service/pullrequest/49015

Discussion here: https://teams.microsoft.com/l/message/19:afba3d1545dd45d7b79f34c1821f6055@thread.skype/1745408179841?tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47&groupId=4d73664c-9f2f-450d-82a5-c2f02756606d&parentMessageId=1745408179841&teamName=.NET%20Core%20Eng%20Services%20Partners&channelName=First%20Responders&createdTime=1745408179841

---
*Migrated from AzDO work item [#8534](https://dev.azure.com/dnceng/internal/_workitems/edit/8534)*

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the markdown-only example in dotnet/runtime#112885 and compare the check status behavior with the recent dotnet-helix-service PR #49015. Reproduce a PR that does not trigger an AzDO pipeline and inspect the Build Analysis and Helix Queue Insights check entry points. Done means these checks no longer remain waiting when no AzDO build exists.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, csharp
Domain
ci-cd, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.