Closed Bug 911136 Opened 12 years ago Closed 11 years ago

Allow editing of relevant slavealloc fields directly from slave health

Categories

(Release Engineering :: General, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: emorley, Assigned: coop)

References

Details

(Keywords: sheriffing-P2, Whiteboard: [slavehealth][slavealloc])

It would be helpful if the slave health pages, eg: https://secure.pub.build.mozilla.org/builddata/reports/slave_health/slave.html?name=talos-r4-lion-031 ...linked to slavealloc for that slave, so sheriffs can quickly jump to slavealloc to disable the slave (and not have to load the main slavealloc UI, wait for the UI to stop hanging and copy/paste the slave name etc). Thank you! :-)
Keywords: sheriffing-P2
slavealloc doesn't make this easy, unfortunately. AFAICT, you can't provide a slavename or pattern and have the slavealloc display limited automatically. I would much rather have the slavealloc information editable directly in slave health. Would that be acceptable?
Priority: -- → P3
Whiteboard: [slavehealth][slavealloc]
(In reply to Chris Cooper [:coop] from comment #1) > I would much rather have the slavealloc information editable directly in > slave health. Would that be acceptable? Definitely :-)
Blocks: 821883
(In reply to (Away 12th-20th July) [:edmorley] from comment #2) > (In reply to Chris Cooper [:coop] from comment #1) > > I would much rather have the slavealloc information editable directly in > > slave health. Would that be acceptable? Question about scope here: How many fields in slavealloc do sheriffs actually use? I'm guessing Notes and Enabled? only, which would make this quicker to a useful first implementation.
(In reply to Chris Cooper [:coop] from comment #3) > How many fields in slavealloc do sheriffs actually use? I'm guessing Notes > and Enabled? only, which would make this quicker to a useful first > implementation. Correct :-)
Assignee: nobody → coop
Status: NEW → ASSIGNED
Priority: P3 → P2
Summary: Add a link to slavealloc from the slave health page → Allow editing of relevant slavealloc fields directly from slave health
This is live now. Please file follow-up bugs for issues.
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Depends on: 1047491
Component: Tools → General
You need to log in before you can comment on or make changes to this bug.