Buildduty regularly pings the loaner bugs and determines if they are still needed or can be returned to the pool. This should be automated. So then we'll have more time to write more tools :-) http://xkcd.com/1319/
Component: Tools → Buildduty
QA Contact: hwine → bugspam.Callek
This is quite handy. Adding :aselagea as adding more scripts to test this might be of his interest. Note explaining the priority level: P5 doesn't mean we've lowered the priority, but the contrary. However, we're aligning these levels to the buildduty quarterly deliverables, where P1-P3 are taken by our daily waterline KTLO operational tasks.
Priority: -- → P5
Could someone offer me some info related to this bug, please? I am thinking to take it. Is this related to the build-slaveapi repository?
Nevermind. I found it! :)
Since we plan to migrate to Taskcluster I don't think we should spend more time on this bug. Just to keep in mind the idea and maybe use it for the new dashboard that will replace Slavehealth.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → WONTFIX
Yeah. I think this should definitely make it to the new tools. It's important to be consistent and create ourselves the (automatic) habits of checking-in with the loaners.
You need to log in before you can comment on or make changes to this bug.