Tracking the work to get Thunderbird building on Firefox infrastructure.
From what I understand, the plan is to complete this work before April 30, when we'll need to move out of sjc1 and leave the momo infrastructure behind. My understanding at the moment is that everything in the momo rack, as well as the tb2-darwin* slaves, will not be moving to scl3. Please either confirm that or correct me?
Dustin: What are your requirements/constraints? What will happen to any hardware we leave behind? Specifically, what hardware are you referring to in this context - build slaves only? Or also our thumper file server, admin boxes, etc..? Thanks.
Any hardware we leave behind will be disposed of as of April 30 if it's still in sjc1. In this bug I'm specifically interested in no longer requiring any of the momo build infrastructure, primarily meaning slaves, but also masters. As you know, the mac mini slaves are not compatible with scl3, so we must be free of them by the move date. As for thumper and the other systems in that rack -- I didn't realize until today that those systems do more than build. I'm working with gozer separately for the non-build parts of that rack, and at the moment the plan is to move thumper and the blade chassis.
jhopkins: what's your take on whether this work will be done before April 30? I want to make sure we have a bug on file for moving the Thunderbird minis and VMs to mtv (or scl1) in case we need a contingency plan here.
coop: Let's discuss priorities today
(In reply to John Hopkins (:jhopkins) from comment #5) > coop: Let's discuss priorities today Fyi coop is off this week
(In reply to Chris Cooper [:coop] [away until Mar 19] from comment #4) > jhopkins: what's your take on whether this work will be done before April > 30? > > I want to make sure we have a bug on file for moving the Thunderbird minis > and VMs to mtv (or scl1) in case we need a contingency plan here. And I really can't stress enough how tricky that contingency plan would turn out to be. So let's make sure it doesn't come to that.
(In reply to Dustin J. Mitchell [:dustin] from comment #3) > Any hardware we leave behind will be disposed of as of April 30 if it's > still in sjc1. per meeting w/arr, drop-dead power off date of 30april is revised to now be 14may.
Fwiw, what is the plan wrt SeaMonkey, which uses (at least) http://build.mozillamessaging.com/tinderboxpushlog/?tree=SeaMonkey and can use http://build.mozillamessaging.com/buildbot/try/ http://build.mozillamessaging.com/tinderboxpushlog/?tree=ThunderbirdTry ?
(In reply to Serge Gautherie (:sgautherie) from comment #9) > Fwiw, what is the plan wrt SeaMonkey, which uses (at least) > http://build.mozillamessaging.com/tinderboxpushlog/?tree=SeaMonkey We might (likely) need to reinstall tbpl on our own infra to support SeaMonkey -- That lies with me. > and can use > http://build.mozillamessaging.com/buildbot/try/ > http://build.mozillamessaging.com/tinderboxpushlog/?tree=ThunderbirdTry > ? This support likely won't be going away, but SeaMonkey support is not directly part of the plan and if it continues to work will be by accident (though if any of "us" want to supply patches to fix any supporting issues, afaik they will be supported). I agree with both of the above assertions though, fwiw. I don't expect any stuff above to be required to support SeaMonkey going forward, and only in cases where SeaMonkey support is basically "for free" should it matter. As this work pans out I'll be tracking and helping to make adjustments where necessary for SeaMonkey.
(In reply to Justin Wood (:Callek) from comment #10) > I agree with both of the above assertions though, fwiw. (I am still hoping SeaMonkey can manage to continue to share these TB (= FF?) infra, rather than duplicate them. We'll see. Ftr, I'm also dreaming of a Try infra that would support FF, TB and SM (_tests_), but that's an additional step compared to current infra ;->)
(In reply to Justin Wood (:Callek) from comment #10) > We might (likely) need to reinstall tbpl on our own infra to support > SeaMonkey -- That lies with me. "Bug 746208 Submitted"
talos-r3-fed-003 is marked on slavealloc as being used for this bug. If that slave is not needed anymore would you please let me know? Thanks!
All Thunderbird builds are happening on Firefox infrastructure now. Thanks to everyone who helped with this!
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
(In reply to Armen Zambrano G. [:armenzg] - Release Engineer from comment #13) > talos-r3-fed-003 is marked on slavealloc as being used for this bug. > If that slave is not needed anymore would you please let me know? Thanks! jhopkins ^^& Does this slave need reimaging ?
See bug 760124
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.