Add support for retriggering failed jobs
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 68/100
Research direction
Start at the treeherder-cli command entry point and trace how it resolves a revision and inspects failed jobs. Use the decision task's public/actions.json and public/label-to-taskid.json, then follow the Taskcluster authentication and retrigger-multiple action flow. Done means failed jobs on the existing push can be retriggered with an optional count, while printing the action task ID and selected-job count.
Written by the indexing model from the issue text.
Description
It would be useful to retrigger failed jobs directly from treeherder-cli after inspecting a push.
For example:
treeherder-cli <revision> --retrigger-failures
Ideally this would retrigger only the failed jobs on the existing push, with an optional count for running them more than once. It should print the action task ID and confirm how many jobs were selected.
The underlying flow appears to be:
- Resolve the push's decision task and failed Taskcluster task IDs.
- Fetch
public/actions.jsonandpublic/label-to-taskid.jsonfrom the decision task. - Map failed tasks back to labels.
- Authenticate with Taskcluster for the hook scope.
- Trigger the in-tree
retrigger-multipleaction.
This came up after using the CLI to inspect a Try push with 18 unrelated failures. The analysis worked well, but completing the natural next step required a custom Taskcluster script.
- Dominant language
- Rust
- Stars
- 1
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from padenot/treeherder-cli
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
padenot/treeherder-cli#13 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
All issues in padenot/treeherder-cli
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
quarto-dev/q2#1155 ·
Maintainers usually reply within 1 day
-
backlog priority: low ui
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
storytold/vectorcraft#6445 · 1 comment ·
Maintainers usually reply within 1 day
-
area: cli kind:docs priority: P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
tursodatabase/libsql#2312 ·
Maintainers usually reply within 11 days
-
`NodeOwned::size_in_bytes` does not count the `ChildrenNodesOwned` heap allocation (since #216)Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
paritytech/trie#251 ·
Maintainers usually reply within 1 day