[release/10.0] Fix internal Helix queue selection - #132907
Conversation
Sorry, something went wrong.
Restrict the Ubuntu Android queue to Android and Bionic platforms so internal validation does not run every libraries work item on an Android agent. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
Azure Pipelines: Successfully started running 2 pipeline(s). 14 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
Sorry, something went wrong.
|
Tagging subscribers to this area: @dotnet/runtime-infrastructure |
Sorry, something went wrong.
There was a problem hiding this comment.
Pull request overview
Adjusts Helix queue selection for libraries jobs in the release/10.0 branch so internal validation doesn’t inadvertently route non-Android/Bionic work items to the Ubuntu Android queue, which can cause large-scale internal build failures.
Changes:
- Split the Android queue condition so the Ubuntu Android queue is only selected for Android/Bionic platforms.
- Keep public vs non-public behavior for arm/arm64 (public uses Windows Android queue; non-public uses Ubuntu Android queue).
💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.
Sorry, something went wrong.
Reviewers
At least 1 approving review is required to merge this pull request.
Internal builds fail with 2k~ errors in 10.0.
Restrict the Ubuntu Android queue to Android and Bionic platforms so internal validation does not run every libraries work item on an Android agent.
This was made in release/11.0 in https://github.com/dotnet/runtime/pull/125548/changes#diff-cbc8f55c9e8b4fc53ff194be8f6e99b461bbb888220a8ede2e5edb53b947b287.