Add support for cancelling a push's jobs
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
Research direction
Start by tracing how treeherder-cli resolves a revision to its decision task and how retriggering in issue #10 handles Taskcluster authentication. Then inspect the decision task’s public/actions.json and the existing cancel-all action flow to identify how its hook is triggered. Done means a revision can be passed with --cancel-all to cancel that push’s jobs.
Written by the indexing model from the issue text.
Description
It would be handy to cancel a push from treeherder-cli, e.g. after pushing a fixed version to try and wanting to stop the stale one from using up machines.
treeherder-cli <revision> --cancel-all
Treeherder does this with the in-tree cancel-all action, so the flow would be roughly:
- Resolve the push's decision task.
- Fetch
public/actions.jsonfrom it and find thecancel-allaction. - Authenticate with Taskcluster and trigger the action's hook.
This needs the same Taskcluster auth as retriggering in #10, so the two could probably share that work.
- 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 68/100
padenot/treeherder-cli#10 ·
-
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