mozilla-aurora and comm-aurora are now building against the win64-rev2
build image.
mozilla-beta and comm-beta will follow suit next week (for beta 1), as
planned.
Thanks,
John
On 13-12-03 2:49 PM, John Hopkins wrote:
> Status of the Windows build image upgrade from [1]:
>
> * mozill
Status of the Windows build image upgrade from [1]:
* mozilla-central and comm-central branches are building only on win64-rev2
* mozilla-inbound and b2g-inbound remain on a mixed rev1/rev2 pool to
ensure an adequate number of build slaves to meet its high checkin load
* 24 win64-rev1 build machin
Status so far:
* The try, mozilla-inbound, b2g-inbound, and try-comm-central branches
have been running on a mixed win64-rev1 + win64-rev2 pool since October
31st.
* Project branches have been building solely on win64-rev2 since October
10th.
* Builds on the cedar and fx-team branches passed smok
lla.org/build/buildbot-configs/file/production/mozilla/production_config.py#l33
>
> On 2013-10-17 2:34 PM, John Hopkins wrote:
>> Here are three different proposals to cut over to the new Windows 64-bit
>> rev2 (win64-rev2) machines (see
>> https://groups.google.com/forum/#!topi
Here are three different proposals to cut over to the new Windows 64-bit
rev2 (win64-rev2) machines (see
https://groups.google.com/forum/#!topic/mozilla.dev.platform/zACrUe_JwKw
for context), along with some of the pros and cons of each approach.
I would prefer option #3 (gradual phase-in) so long
On 13-10-10 4:25 PM, John Hopkins wrote:
>
> Project branches are cutting over to the new win64-rev2 build machines.
Project branch builds have run overnight on the new build machines and
are looking good.
We will continue migrating more branches next week.
John
> On 13-10-09 5:22
Project branches are cutting over to the new win64-rev2 build machines.
John
On 13-10-09 5:22 PM, John Hopkins wrote:
> Release Engineering is migrating the Windows 64-bit _build_ machines to
> a new, managed machine image which will decrease the amount of
> administrative overhead
t-person on Release
> Engineering that we should pull into the testing discussion?
This switchover is specifically for the build machines, not test
machines. You probably want bug 886640.
Thanks,
John
> - Original Message -----
> From: "John Hopkins"
> To: "dev.platform&
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
In an earlier blog post[1] I explained how Release Engineering are moving the
mozilla-central, try, and project branch Linux 32- and 64-bit builds to our new
platform. This change allows us to do builds in the cloud as required and in
response to build demand.
Now that testing is complete, w
10 matches
Mail list logo
