On 2014-03-11, 2:07 PM, Ben Hearsum wrote: > On 03/11/14 01:51 PM, Gregory Szorc wrote: >> The only major question I have is over the impact to release automation. >> I'm not sure to what degree they rely on MozillaBuild, if any. We want >> the build environments to remain as similar as possible to prevent >> surprises. It would be great if you could get a commitment from >> automation to transition to msys2 at or around the same time as >> MozillaBuild. IIRC they are talking about moving their Windows infra out >> of Mozilla data centers and into the cloud. So now would seem like the >> best time to approach them with this looming requirement. > > Our automation uses a heavily patched older version of MozillaBuild > (based on 1.2 or 1.3 IIRC). With recent changes to how we deploy things > on Windows, it might be easier. > > One complication is how we support older branches. If this is something > that requires in tree changes that ride the trains, supporting older > branches may get very complicated, because Buildbot runs inside of > MozillaBuild, so delegating to a different set of tools from inside of > Buildbot may not be possible.
That said, we would make every reasonable effort to support this change. Package installation and maintenance on Windows has gotten better with our recent move to GPO, but as Ben says, we're still layering newer versions of required tools over-top of an ancient MozillaBuild install. Having an easier way to update and experiment would be great. Is part of the plan to keep a manifest of required tool versions in the tree, similar to what we do now with tooltool? cheers, -- coop _______________________________________________ dev-builds mailing list dev-builds@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-builds
