1518927 - Worker Manager should be able to sort by last-seen, task-state, last-resolved

Status: RESOLVED MOVED

(Taskcluster :: Services, enhancement)

Description

[Jordan Lund (:jlund)]

this would be an improvement over current explorer UI.

Comment 1

[[:owlish] 🦉 PST]

I started working on the new worker manager ui, and I'd like some clarification here. Is the requested the requested functionality for lists of the worker types? Am I guessing the meaning of the columns correctly:
last-seen - last time a worker of this type was active,
task-state - number of failed tasks,
last-resolved - last time when a task was resolved

Comment 2

[Jordan Lund (:jlund)]

(In reply to [:owlish] from comment #1)

I started working on the new worker manager ui, and I'd like some clarification here. Is the requested the requested functionality for lists of the worker types? Am I guessing the meaning of the columns correctly:

Thanks for this!

task-state - number of failed tasks,

I believe what we would like is a way to be able to sort by all types of non success/green. So exception, retry, failed etc.

Similar to bug 1518928, I will be on leave until June 12th. Could you please reach out to Danut Labici for further user input / questions regarding this bug? I've cc'd the ciduty team account to this bug

Comment 3

[Dustin J. Mitchell [:dustin] (he/him)]

@owlish does this block the tc-cloudops migration?

Comment 4

[[:owlish] 🦉 PST]

[I duplicate this answer in the two similar tickets] Currently, I don't work on the UI because AWS provider is prioritized. I will return to the worker manager UI once I'm done with AWS provider. I don't think this blocks tc-cloudops migration.... However, maybe if you give me some background info on what prompted you to ask this question (i.e. what makes you think this might be blocking tc-migration; or to rephrase further, what are possible ways this can block the migration), I might be able to give more definitive answer

Comment 5

[Dustin J. Mitchell [:dustin] (he/him)]

It's in the dependency tree for the "tc-cloudops" bug, is why I ask. I can fix that up. The way it might block the migration is my representing an existing functionality that users would lose during the migration if the bug isn't completed. I agree that it doesn't block the migration.

Comment 6

[Dustin J. Mitchell [:dustin] (he/him)]

https://github.com/taskcluster/taskcluster/issues/2881