If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Find a better way to deal with requests for loaner slaves

RESOLVED FIXED

Status

Release Engineering
Buildduty
P2
normal
RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: philor, Assigned: coop)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

4 years ago
I'm not sure exactly what way would work for releng, but I'm absolutely sure that the current method, where people file in the generic Release Engineering bucket, almost never knowing that they should bring it to [buildduty]'s attention with the whiteboard, and then they either get their slave because they know to hound buildduty on IRC, or they just never actually get their slave, is not working.

The one thing I know would work is mozilla.org::Release Engineering: Loaner slaves.

See bug 877865 and bug 843307 as random examples I ran across tonight of just how much the current system is not working - neither 7 days for someone trying to reproduce a probably sec-critical bug that can no longer be reproduced on the slaves we run on trunk/try, nor 107 days with absolutely no word whatsoever, not even a WONTFIX, are the kind of loaner results we should have.
(Reporter)

Updated

4 years ago
Blocks: 877865, 843307
(Reporter)

Updated

4 years ago
Blocks: 877297

Comment 1

4 years ago
I agree 100%. I will bring it up to the team.
(Assignee)

Comment 2

4 years ago
This dovetails nicely with the discussion jhopkins started last week re: fixing the end-to-end process of loaning slaves. We have a similar problem on the opposite end of the process where re-imaged slaves languish before making it back into production.

Armen: is this something you have time to drive before you go on vacation, or should I assign it to someone else?
(Assignee)

Updated

4 years ago
Assignee: nobody → coop
Status: NEW → ASSIGNED
Priority: -- → P2
Found in triage. 

Coop put a lot of thought into the new components in bug#898244 ti help along with changes to buildduty docs. Anything else to do here?
Flags: needinfo?(coop)
(Assignee)

Comment 4

4 years ago
(In reply to John O'Duinn [:joduinn] from comment #3)
> Found in triage. 
> 
> Coop put a lot of thought into the new components in bug#898244 ti help
> along with changes to buildduty docs. Anything else to do here?

Yes, quite a bit actually.

I'm on buildduty this week, so I may finally have time to formalize the process and write it down, create loaner queries, etc.
Flags: needinfo?(coop)
(mass move of loan bugs to new releng component, filter on CallekAug2013LoanerMove )
Component: Release Engineering → Release Engineering: Loan Requests
Product: mozilla.org → Release Engineering

Updated

4 years ago
Component: Loan Requests → Buildduty

Comment 6

4 years ago
This got completed with formalization through https://wiki.mozilla.org/ReleaseEngineering/How_To/Request_a_slave

We also have a "Loan Requests" component plus we're improving the quality of buildduty periods.
Status: ASSIGNED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.