Closed Bug 842052 Opened 9 years ago Closed 8 years ago

Link the slave name to the new slave health dashboard rather than the buildapi recent jobs page


(Tree Management Graveyard :: TBPL, enhancement)

Not set


(Not tracked)



(Reporter: philor, Assigned: emorley)



(Keywords: sheriffing-P1)


(1 file)

Although there are times when buildapi/recent is what I want to know about a slave, particularly in the case of OS X when looking at an unfiled failure the first thing I want to know is whether there's a problem tracking bug for that slave filled with "this slave is busted, look at this crash and this timeout and these pink pixel of death failures" comments, so rather than clicking the linked slavename, I (carefully, because selecting linked text is always awkward) select it and search Bugzilla for it.

Conveniently, already has exactly what we need to steal, behind the white-on-blue ? icons: look up whether there's a bug, what its status is if there is, and offer to let you file one if there isn't one.
Ryan, want to chat through this one at some point and then see if it's something you'd like to take on?
Keywords: sheriffing-P1
last-job-per-slave.html uses things like:
<img src="./icons/help.png" alt="Check bug status" title="Check bug status" onclick="getBugByAlias("talos-r3-xp-020");">

Which uses:
17:07:46 - edmorley: philor: for bug 842052, would pointing at eg: be an acceptable solution?
Assignee: nobody → emorley
Summary: Steal the code to look up or file a slave problem tracking bug from last-job-per-slave.html → Link the slave name to the new slave health dashboard rather than the buildapi recent jobs page
Attached patch Patch v1Splinter Review
Attachment #772692 - Flags: review?(philringnalda)
Comment on attachment 772692 [details] [diff] [review]
Patch v1

Looks good.
Attachment #772692 - Flags: review?(philringnalda) → review+
Depends on: 891621
In production :-)
Closed: 8 years ago
Resolution: --- → FIXED
Product: Webtools → Tree Management
Product: Tree Management → Tree Management Graveyard
You need to log in before you can comment on or make changes to this bug.