Open
Bug 1160187
Opened 10 years ago
Updated 8 years ago
Address redundancies in Job: 'name' jobSearchStr string
Categories
(Tree Management :: Treeherder: Frontend, defect, P3)
Tree Management
Treeherder: Frontend
Tracking
(Not tracked)
NEW
People
(Reporter: jfrench, Unassigned)
References
()
Details
I assume we inherit it all upstream, but there are some examples where the job artifact is, say:
job_group_name: "Mochitest e10s"
job_group_symbol: "M-e10s"
job_type_name: "Mochitest e10s Browser Chrome"
job_type_symbol: "bc1"
And we end up with this hugely long job "name" with replicated words in the Job details panel:
Windows 8 x64 pgo Mochitest e10s Mochitest e10s Browser Chrome M-e10s(bc2)
For the purposes of readability, and for retrigger notifications (see bug 1057260) I just wonder if we should be doing anything about it.
Some choices:
a) do nothing, leave it as-is
b) if there is no impact reduce the current fields used for jobSearchStr in
https://github.com/mozilla/treeherder-ui/blob/c1afbee2bd6b97f7d67c552b47769933e7abb510/webapp/app/js/services/main.js#L238-L244
c) render a subset of those values as the job 'name', and create a new, small, "keywords" filter link similar to our signature - which uses all the current jobSearchStr values
d) some combination of the above... or something else?
Updated•8 years ago
|
Component: Treeherder → Treeherder: Frontend
You need to log in
before you can comment on or make changes to this bug.
Description
•