Closed
Bug 1053203
Opened 10 years ago
Closed 6 years ago
Treeherder help "Builds & Tests" section should be removed
Categories
(Tree Management :: Treeherder, defect, P5)
Tree Management
Treeherder
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Sylvestre, Assigned: jfrench, Mentored)
References
()
Details
(Keywords: good-first-bug, Whiteboard: [lang=js])
Attachments
(1 file)
On this page: https://treeherder.allizom.org/ui/help.html the builds & tests section should be automatically generated from the database and the description should be displayed too.
Comment 1•10 years ago
|
||
Ah I didn't realise it was hardcoded :( https://github.com/mozilla/treeherder-ui/blob/master/webapp/app/help.html I'd filed bug 1052489 for this, but let's keep this bug and make bug 1052489 just about the tooltips.
Summary: Treeherder help Builds & Tests section should be generated from the db → Treeherder help "Builds & Tests" section should be generated from the db
Updated•9 years ago
|
Priority: P3 → P5
Assignee | ||
Comment 2•9 years ago
|
||
We've mad made further customizations to the Builds/Tests sections, manually adding links for Spidermonkey and other jobs for Releng eg. https://github.com/mozilla/treeherder-ui/pull/395/files and https://github.com/mozilla/treeherder-ui/pull/394. I am not sure if it precludes auto generation, but it seems to be evolving more towards a manually maintained model.
Comment 3•9 years ago
|
||
I'm still not keen on hardcoding things in help and having to keep them up to date. Also, to me, help shouldn't really be about lists of job names and links to their info (that should be somewhere else), but instead actual help about the webapp :-)
Assignee | ||
Comment 4•9 years ago
|
||
+1. I think those Build/Tests tables might be suitable for RTD, or something similar. :) We also have in-app tooltips on each job element which kind of replicates the information, and those often seem more informative.
Updated•7 years ago
|
Priority: P5 → --
Updated•6 years ago
|
Summary: Treeherder help "Builds & Tests" section should be generated from the db → Treeherder help "Builds & Tests" section should be removed
Comment 5•6 years ago
|
||
In triage with Ed: We agree that this data gets out of date too quickly and doesn't add anything more useful than you would get by just hovering or selecting the job type in question. So if more data about a job could be provided, it should reside upstream in TaskCluster somewhere. But the data in these sections really isn't useful and should be removed.
Updated•6 years ago
|
Comment 6•6 years ago
|
||
The relevant code is here: https://github.com/mozilla/treeherder/blob/9f0a90343c4940c866074726c4f05fdfa22ac4d8/ui/userguide.html#L171-L407
Assignee | ||
Updated•6 years ago
|
Assignee: nobody → tojonmz
Status: NEW → ASSIGNED
Comment 7•6 years ago
|
||
Assignee | ||
Comment 8•6 years ago
|
||
Comment on attachment 8945180 [details] [review] Link to GitHub pull-request: https://github.com/mozilla/treeherder/pull/3164 Purge ahoy :)
Attachment #8945180 -
Flags: review?(emorley)
Comment 9•6 years ago
|
||
Comment on attachment 8945180 [details] [review] Link to GitHub pull-request: https://github.com/mozilla/treeherder/pull/3164 One small tweak :-)
Attachment #8945180 -
Flags: review?(emorley) → review-
Assignee | ||
Comment 10•6 years ago
|
||
Comment on attachment 8945180 [details] [review] Link to GitHub pull-request: https://github.com/mozilla/treeherder/pull/3164 Ok, I think ready to go now.
Attachment #8945180 -
Flags: review- → review?(emorley)
Comment 11•6 years ago
|
||
Comment on attachment 8945180 [details] [review] Link to GitHub pull-request: https://github.com/mozilla/treeherder/pull/3164 Many thanks!
Attachment #8945180 -
Flags: review?(emorley) → review+
Comment 12•6 years ago
|
||
Commit pushed to master at https://github.com/mozilla/treeherder https://github.com/mozilla/treeherder/commit/247e1b980ce98048fc3df12416d6bb6f1fe4d582 Bug 1053203 - Remove builds and tests tables from user guide (#3164)
Updated•6 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•