I think we could have it happen in this order: 1. a way to green up tests on a single machine hooked up to a build server 2. put this on Try 3. put this on production automation
Of course, it would be awesome if we could skip #1 and go to #2 directly as we green up the tests, as this will open it up to multiple contributors for the test greening. --Jet ----- Original Message ----- From: "Ben Hearsum" <bhear...@mozilla.com> To: dev-platform@lists.mozilla.org Sent: Wednesday, October 9, 2013 2:50:52 PM Subject: Re: Migrating to Win64 rev2 machines Hey Jet, I'd say that this greenery project is completely aside from the work John is doing -- build and tests machines are generally separate. Are you looking for you (or someone else) to have access to a machine to green up tests on your own, or looking to have tests run as part of the normal automation (or maybe on Try?)? - Ben On 10/09/13 05:35 PM, Jet Villegas wrote: > I'm currently looking for someone to green up the tests on Win64. Can we > dedicate one machine instance (I'm assuming this is on AWS?) for the purpose > of advancing this greenery project? Also, who is the point-person on Release > Engineering that we should pull into the testing discussion? > > Thanks, > > --Jet > > ----- Original Message ----- > From: "John Hopkins" <jhopk...@mozilla.com> > To: "dev.platform" <dev-platform@lists.mozilla.org> > Cc: sheri...@mozilla.com > Sent: Wednesday, October 9, 2013 2:22:52 PM > Subject: Migrating to Win64 rev2 machines > > Release Engineering is migrating the Windows 64-bit _build_ machines to > a new, managed machine image which will decrease the amount of > administrative overhead needed to deploy new instances, make image > changes, etc. > > It uses the same build toolchain as the current Windows 64-bit images > (MSVC10) but located at different paths so you'll notice conditional > checks like > http://hg.mozilla.org/mozilla-central/file/a141e39bf6da/build/win64/mozconfig.vs2010#l2 > which will be uplifted. > > The 'cedar' project branch has been building successfully using the new > image. The plan is to migrate other branches over the next few weeks in > this order: > - remaining project branches > - mozilla-central > - mozilla-inbound, b2g-inbound > - try > - aurora > - beta > - release, mozilla-b2g18* > - esr > > Wait times may increase for a short time on days that we cut over to the > new build machines (since we are reimaging existing machines in chunks). > We'll be keeping an eye on those wait times and adjusting the number of > machines cut over if needed. Thunderbird comm-* branches will be cut > over at the same time as their mozilla-* counterpart. > > The project branches will be cut over tomorrow and we'll let those build > over the weekend before cutting over mozilla-central. I will send an > email notification on this thread before and after a cutover so everyone > knows the current status. > > Bug 781277 tracks this effort. If you have any questions or concerns, > please let me know. > > Thanks, > John > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
