Add an "auto-bisect" tool that can bisect AzDO builds to find the first failing commit #122657
Conversation
github-actions
bot
added
the
needs-area-label
There was a problem hiding this comment.
nit: dotnet sln migrate src/tools/auto-bisect/auto-bisect.sln to replace it with slnx variant (entire repo is on slnx plan now: git ls-files ':/*slnx | wc -l' vs. git ls-files ':/*sln | wc -l').
am11
added
area-Infrastructure
and removed
needs-area-label
|
Tagging subscribers to this area: @dotnet/runtime-infrastructure |
| export AZDO_PAT=<token> | ||
| dotnet run -- bisect \ | ||
| -o <org> -p <project> \ | ||
| --good <build-id> --bad <build-id> \ | ||
| --test <test-name> |
There was a problem hiding this comment.
Maybe it can be added as github workflow (like backport.yml), with a comment trigger on issues and pulls:
/bisect <good> <bad> <test-name>
|
|
||
| **Requirements:** | ||
|
|
||
| 1. A personal AzDO PAT with read & execute permission for the "Build" tasks, and read for "Test Management". |
There was a problem hiding this comment.
If I am understanding this correctly you might want to make it more clear that this is limited to being an employee so that contributors that find this documentation don't struggle with permission issues.
3 participants
auto-bisect
A tool for automatically finding the first commit that introduced a test failure in Azure DevOps builds using binary search. Given a known good build and a known bad build, it will automatically queue builds (or use existing ones) to test commits in between, narrowing down to the exact commit that caused the regression.
I built this to help track down outerloop failures.