Closed Bug 1164184 Opened 5 years ago Closed 4 years ago

Add UI for increasing and decreasing the priority of jobs using the self-serve api


(Tree Management :: Treeherder, defect)

Not set


(Not tracked)



(Reporter: emorley, Unassigned)


Inspired by bug 701548.
Does taskcluster have equivalent functionality? If not, this can be wontfixed, since we're moving away from buildapi.
Flags: needinfo?(armenzg)
Hey Jonas,
Is part of the roadmap to give various priorities to tasks?

This is useful for pools with limited resources and certain repositories being less important (e.g. try compared to mozilla-central).
Flags: needinfo?(armenzg) → needinfo?(jopsen)
We recently introduced task.priority, see:
As evident from docs we have priorities:
  - "normal" (default)
  - "high"

As expected priority "high" is higher than normal :)
And creating a task with it requires the scope "queue:task-priority:high".

You cannot change priority after task submission (technically we could support it).
But I think that it's very powerful to maintain immutability of task definitions,
so I would rather not change that.

But you could retrigger/recreate tasks with higher priority and cancel existing tasks.

Our priority levels are strictly discrete, and adding another priority level is expensive in terms of
polling overhead. Preferably 2 priorities should be sufficient, but we could introduce another one.
Flags: needinfo?(jopsen)
Thank you for the explanation. Sounds like this bug isn't needed post buildapi (one less thing to clutter up the Treeherder UI \o/) :-)
Closed: 4 years ago
Resolution: --- → WONTFIX
Thanks jonasfj. This was very helpful. My apologies if I did not go first to the docs.
You need to log in before you can comment on or make changes to this bug.