Closed
Bug 924503
Opened 11 years ago
Closed 11 years ago
Turn off the B2G builds marked as REMOVE on https://wiki.mozilla.org/User:Asasaki:B2GBuilds -- proceed turning off Unagi per :stephend
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mozilla, Assigned: mozilla)
References
Details
Attachments
(5 files)
2.83 KB,
patch
|
rail
:
review+
mozilla
:
checked-in+
|
Details | Diff | Splinter Review |
3.91 KB,
patch
|
Details | Diff | Splinter Review | |
17.35 KB,
patch
|
nthomas
:
review+
mozilla
:
checked-in+
|
Details | Diff | Splinter Review |
6.66 KB,
patch
|
nthomas
:
review+
mozilla
:
checked-in+
|
Details | Diff | Splinter Review |
4.11 KB,
patch
|
nthomas
:
review+
mozilla
:
checked-in+
|
Details | Diff | Splinter Review |
We've been asking for a list of b2g builds we can turn off; we've gotten that list. _ QA signoff _ WebQA signoff _ ATeam signoff _ patch(es) _ review _ land _ reconfig
Assignee | ||
Comment 1•11 years ago
|
||
:tchung, :stephend, :jgriffin - does this list of REMOVE builds look ok? (from b2g eng managers) https://wiki.mozilla.org/User:Asasaki:B2GBuilds
Flags: needinfo?(tchung)
Flags: needinfo?(stephen.donner)
Flags: needinfo?(jgriffin)
Comment 2•11 years ago
|
||
(In reply to Aki Sasaki [:aki] from comment #1) > :tchung, :stephend, :jgriffin - does this list of REMOVE builds look ok? > (from b2g eng managers) > https://wiki.mozilla.org/User:Asasaki:B2GBuilds I'm good with this list. :stephend will make the final edits and reply back here.
Flags: needinfo?(tchung)
Comment 3•11 years ago
|
||
This list implies that we're turning off all testing on mozilla-b2g18/mozilla-b2g18-v1.1.0hd, which is fine if that's the agreement with the b2g engineering managers.
Flags: needinfo?(jgriffin)
Comment 4•11 years ago
|
||
(In reply to Aki Sasaki [:aki] from comment #1) > :tchung, :stephend, :jgriffin - does this list of REMOVE builds look ok? > (from b2g eng managers) > https://wiki.mozilla.org/User:Asasaki:B2GBuilds LGTM, with the following caveat: If we kill Unagi on master/Aurora for the engineering builds, before I can get Inaris to our Softvision contractors, that will severely limit/kill their Gaia UI Tests involvement. If you would, can we kill/remove Unagi on master/Aurora, last? Thanks!
Flags: needinfo?(stephen.donner)
Assignee | ||
Comment 5•11 years ago
|
||
Per last week's Tuesday B2G meeting, we want to keep some of these old build binaries around as well (possibly as little as the final build of each type). We want to keep unagi on m-c/aurora for last, per comment 4. We want to keep emulator builds on 1.1hd for now, since turning them off would turn off automated testing. We may get confirmation on this later.
Assignee | ||
Comment 6•11 years ago
|
||
It's another for loop, which I don't like. But it lets us turn these back on quickly if we need. Come December we'll actually tear out all the 1.0.1 stuff completely, and the configs will be slightly less ugly. I'm leaving unagi/unagi-eng on aurora+central for now. I'm also leaving b2g18_v1_1_0_hd emulator builds, for automation testing.
Assignee: nobody → aki
Attachment #814678 -
Flags: review?(rail)
Assignee | ||
Comment 7•11 years ago
|
||
Builder interdiff, for a build master.
Comment 8•11 years ago
|
||
Comment on attachment 814678 [details] [diff] [review] bug924503 part 1 woohoo!
Attachment #814678 -
Flags: review?(rail) → review+
Updated•11 years ago
|
Summary: turn off the REMOVE builds https://wiki.mozilla.org/User:Asasaki:B2GBuilds → Turn off the B2G builds marked as REMOVE on https://wiki.mozilla.org/User:Asasaki:B2GBuilds
Comment 9•11 years ago
|
||
(Have CCed the sheriffs alias so we don't end up thinking builds have gone missing :-))
Assignee | ||
Comment 10•11 years ago
|
||
Comment on attachment 814678 [details] [diff] [review] bug924503 part 1 https://hg.mozilla.org/build/buildbot-configs/rev/707b23430c3d
Attachment #814678 -
Flags: checked-in+
Comment 11•11 years ago
|
||
in production
Assignee | ||
Comment 12•11 years ago
|
||
X QA signoff X WebQA signoff X ATeam signoff X Verify we want automated testing off on 1.1 and 1.1hd ** We kept emulator builds on 1.1hd for automated tests. X patch(es) X review X land X reconfig X update https://wiki.mozilla.org/User:Asasaki:B2GBuilds _ wait for WebQA to get Inaris to Softvision <-- WE ARE HERE _ patch to turn off unagi on m-c and m-a _ review _ land _ reconfig _ update https://wiki.mozilla.org/User:Asasaki:B2GBuilds _ RESO FIXED Setting needinfo? for :stephend, so we know when to turn off the unagi builds on m-c and m-a.
Flags: needinfo?(stephen.donner)
Comment 13•11 years ago
|
||
(In reply to Aki Sasaki [:aki] from comment #12) > X QA signoff > X WebQA signoff > X ATeam signoff > X Verify we want automated testing off on 1.1 and 1.1hd > ** We kept emulator builds on 1.1hd for automated tests. per meeting w/clee, tchung just now, we now officially *do* need to keep these emulator builds on v1.1HD. I've updated https://wiki.mozilla.org/User:Asasaki:B2GBuilds to match new reality. > X patch(es) > X review > X land > X reconfig > X update https://wiki.mozilla.org/User:Asasaki:B2GBuilds > _ wait for WebQA to get Inaris to Softvision <-- WE ARE HERE > _ patch to turn off unagi on m-c and m-a > _ review > _ land > _ reconfig > _ update https://wiki.mozilla.org/User:Asasaki:B2GBuilds > _ RESO FIXED > > Setting needinfo? for :stephend, so we know when to turn off the unagi > builds on m-c and m-a.
Assignee | ||
Comment 14•11 years ago
|
||
So you're ready for these to be turned off now? I can write the patch shortly.
Assignee | ||
Updated•11 years ago
|
Summary: Turn off the B2G builds marked as REMOVE on https://wiki.mozilla.org/User:Asasaki:B2GBuilds → Turn off the B2G builds marked as REMOVE on https://wiki.mozilla.org/User:Asasaki:B2GBuilds -- proceed turning off Unagi per :stephend
Assignee | ||
Comment 15•11 years ago
|
||
Hm, now I'm wondering if this was intentional. Was it? Since that happened at the same time as marking bug 932381 as blocking, this might have been inadvertent...
Flags: needinfo?(stephen.donner)
(In reply to Aki Sasaki [:aki] from comment #15) > Hm, now I'm wondering if this was intentional. Was it? > Since that happened at the same time as marking bug 932381 as blocking, this > might have been inadvertent... Yes, sorry: intentional. We need to ensure that the in-country Marketplace Payments testers (third-party contractors) are set up properly with ezboot on Inari, since they're moving off Unagis, as our (Web QA) final dependency to moving off Unagis, wholesale.
Flags: needinfo?(stephen.donner)
Updated•11 years ago
|
Flags: needinfo?(stephen.donner)
Assignee | ||
Comment 17•11 years ago
|
||
Assignee | ||
Comment 18•11 years ago
|
||
Assignee | ||
Comment 19•11 years ago
|
||
Assignee | ||
Comment 20•11 years ago
|
||
Sorry, still not clear. Are you saying that yes, it's intentional that you cleared the needinfo flag (which you have re-set), and you want the Unagi builds off now? The dependency seems like you may want us to wait. For clarity's sake, could you say the equivalent of "Please turn off the Unagi builds now" when you're ready? I'll set the review flags at that point, and we can land+reconfig+update the wiki and resolve this bug.
Assignee | ||
Updated•11 years ago
|
Attachment #826370 -
Flags: review?(nthomas)
Assignee | ||
Comment 21•11 years ago
|
||
Comment on attachment 826371 [details] [diff] [review] unagi-mozharness.diff also removing old otoro references.
Attachment #826371 -
Flags: review?(nthomas)
Assignee | ||
Updated•11 years ago
|
Attachment #826372 -
Flags: review?(nthomas)
(In reply to Aki Sasaki [:aki] from comment #20) > Sorry, still not clear. > > Are you saying that yes, it's intentional that you cleared the needinfo flag > (which you have re-set), and you want the Unagi builds off now? > The dependency seems like you may want us to wait. Apologies; the dependency I added -- bug 932381 -- needs to be fixed and its replacement in-use by third-party contractors, before I can sign off. > For clarity's sake, could you say the equivalent of "Please turn off the > Unagi builds now" when you're ready? I'll set the review flags at that > point, and we can land+reconfig+update the wiki and resolve this bug. Yes, I can + will, sorry again for the confusion!
Flags: needinfo?(stephen.donner)
Updated•11 years ago
|
Flags: needinfo?(stephen.donner)
Updated•11 years ago
|
Attachment #826370 -
Flags: review?(nthomas) → review+
Comment 23•11 years ago
|
||
Comment on attachment 826371 [details] [diff] [review] unagi-mozharness.diff >diff --git a/configs/b2g/releng-otoro.py b/configs/b2g/releng-otoro.py Might be worth renaming this to something more descriptive, at some point when we have cycles for such niceties.
Attachment #826371 -
Flags: review?(nthomas) → review+
Comment 24•11 years ago
|
||
Comment on attachment 826372 [details] [diff] [review] unagi-tools.diff seems fine *stamp*
Attachment #826372 -
Flags: review?(nthomas) → review+
Comment 25•11 years ago
|
||
(In reply to Stephen Donner [:stephend] from comment #22) > (In reply to Aki Sasaki [:aki] from comment #20) > > Sorry, still not clear. > > > > Are you saying that yes, it's intentional that you cleared the needinfo flag > > (which you have re-set), and you want the Unagi builds off now? > > The dependency seems like you may want us to wait. > > Apologies; the dependency I added -- bug 932381 -- needs to be fixed and its > replacement in-use by third-party contractors, before I can sign off. > > > For clarity's sake, could you say the equivalent of "Please turn off the > > Unagi builds now" when you're ready? I'll set the review flags at that > > point, and we can land+reconfig+update the wiki and resolve this bug. > > Yes, I can + will, sorry again for the confusion! sdonner: gentle ping about turning off unagi builds? I see all dep bugs now resolved, including bug#932381, hence the ask.
(In reply to John O'Duinn [:joduinn] from comment #25) > (In reply to Stephen Donner [:stephend] from comment #22) > > (In reply to Aki Sasaki [:aki] from comment #20) > > > Sorry, still not clear. > > > > > > Are you saying that yes, it's intentional that you cleared the needinfo flag > > > (which you have re-set), and you want the Unagi builds off now? > > > The dependency seems like you may want us to wait. > > > > Apologies; the dependency I added -- bug 932381 -- needs to be fixed and its > > replacement in-use by third-party contractors, before I can sign off. > > > > > For clarity's sake, could you say the equivalent of "Please turn off the > > > Unagi builds now" when you're ready? I'll set the review flags at that > > > point, and we can land+reconfig+update the wiki and resolve this bug. > > > > Yes, I can + will, sorry again for the confusion! > > sdonner: gentle ping about turning off unagi builds? I see all dep bugs now > resolved, including bug#932381, hence the ask. Just today, I sent out the final (approved) Inari device to Intertek, to test in-country Payments; there's a meeting tomorrow to hash out how we can go forward for other third-party contractors WRT Inaris + other devices, but we should be good to switch off Unagi pretty soon. cc:ing Edwin, whom I believe might still have a contractor, too, using an Unagi, for the time-being.
Flags: needinfo?(stephen.donner)
Comment 27•11 years ago
|
||
(In reply to Stephen Donner [:stephend] from comment #26) > (In reply to John O'Duinn [:joduinn] from comment #25) > > (In reply to Stephen Donner [:stephend] from comment #22) > > > (In reply to Aki Sasaki [:aki] from comment #20) > > > > Sorry, still not clear. > > > > > > > > Are you saying that yes, it's intentional that you cleared the needinfo flag > > > > (which you have re-set), and you want the Unagi builds off now? > > > > The dependency seems like you may want us to wait. > > > > > > Apologies; the dependency I added -- bug 932381 -- needs to be fixed and its > > > replacement in-use by third-party contractors, before I can sign off. > > > > > > > For clarity's sake, could you say the equivalent of "Please turn off the > > > > Unagi builds now" when you're ready? I'll set the review flags at that > > > > point, and we can land+reconfig+update the wiki and resolve this bug. > > > > > > Yes, I can + will, sorry again for the confusion! > > > > sdonner: gentle ping about turning off unagi builds? I see all dep bugs now > > resolved, including bug#932381, hence the ask. > > Just today, I sent out the final (approved) Inari device to Intertek, to > test in-country Payments; there's a meeting tomorrow to hash out how we can > go forward for other third-party contractors WRT Inaris + other devices, but > we should be good to switch off Unagi pretty soon. sdonner: are you now ok if we drop the axe on these builds? > cc:ing Edwin, whom I believe might still have a contractor, too, using an > Unagi, for the time-being. ewong: do you have a dependency on these builds? If so, how quickly can you switch to another supported device?
Flags: needinfo?(stephen.donner)
Flags: needinfo?(ewong)
John, my extended (both Softvision + Intertek, in-country Marketplace Payments tests) + in-house team are good; thanks -- we're all on Inari and Hamachis, now. From my end, no more need for Unagi builds!
Flags: needinfo?(stephen.donner)
Comment 29•11 years ago
|
||
I'm good with discontinuing unagi builds. It's time for everyone to upgrade!
Flags: needinfo?(ewong)
Assignee | ||
Comment 30•11 years ago
|
||
Comment on attachment 826371 [details] [diff] [review] unagi-mozharness.diff https://hg.mozilla.org/build/mozharness/rev/d163222e0366
Attachment #826371 -
Flags: checked-in+
Assignee | ||
Comment 31•11 years ago
|
||
Comment on attachment 826372 [details] [diff] [review] unagi-tools.diff https://hg.mozilla.org/build/tools/rev/a374a287890d
Attachment #826372 -
Flags: checked-in+
Assignee | ||
Comment 32•11 years ago
|
||
Comment on attachment 826370 [details] [diff] [review] unagi-configs.diff Unbitrotted + landed: https://hg.mozilla.org/build/buildbot-configs/rev/2881515a3e33 Now we need a merge+reconfig and we're done.
Assignee | ||
Updated•11 years ago
|
Attachment #826370 -
Flags: checked-in+
Comment 33•11 years ago
|
||
What sort of retention policy should we have on the builds that have been disabled ? Should they be archived to tape/archived to Amazon S3/deleted outright ?
Assignee | ||
Comment 34•11 years ago
|
||
I merged the mozharness portion into production. (In reply to Nick Thomas [:nthomas] from comment #33) > What sort of retention policy should we have on the builds that have been > disabled ? Should they be archived to tape/archived to Amazon S3/deleted > outright ? I'm not entirely sure, but I know people wanted to keep at least the most recent builds. Archiving to S3 makes sense, but would be dependent on bug 922889.
Assignee | ||
Comment 35•11 years ago
|
||
... which is resolved ok. To the cloud!!!
Assignee | ||
Comment 36•11 years ago
|
||
I'm going to update the b2gbuilds wiki page, and we'll need to archive builds. The builds are all off, though.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Comment 37•11 years ago
|
||
In production.
Updated•6 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•