685178 - Set up Windows 64 bit builders for all Thunderbird & Calendar trees

Status: RESOLVED INVALID

(Mozilla Messaging Graveyard :: Release Engineering, defect)

Description

[Mark Banner (:standard8)]

We need 64 bit builders for all the Thunderbird trees. For rolling this out we should do this order:

1) Thunderbird Try
2) Thunderbird comm-central
3) the rest of Thunderbird comm-* if appropraite

For each step, we need to ensure that a) builds pass and run, b) tests pass consistently.

If we pass a) but fail b) then we may be able to continue the roll out of a) with hiding tests or disabling them depending on what we feel is best and builder load.

At the moment the priorities are for getting builds on 1) and 2).

Comment 1

[John Hopkins (:jhopkins)]

We should split this bug into separate Calendar and Thunderbird requests since they will be running on separate pools of hardware in the near future.

Comment 2

[Philipp Kewisch [:Fallen] [:📆][:🧩]]

Just a side note, there is discussion on disabling 64 bit nightlys in m.d.planning

http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/1a28a3f8065f5003#

Comment 3

[Mark Banner (:standard8)]

(In reply to Philipp Kewisch [:Fallen] from comment #2)
> Just a side note, there is discussion on disabling 64 bit nightlys in
> m.d.planning
> 
> http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/
> 1a28a3f8065f5003#

Nightly but not dep builds I believe (although it may lead there eventually).

Comment 4

[Mark Banner (:standard8)]

The Thunderbird part of this has been done in bug 698843 for Daily only. The rest of this is wontfix until it is decided to roll-out 64 bit builds across the development system - currently this is not a high priority for Mozilla at the moment as per the recent thread on mozilla.dev.planning (http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/1a28a3f8065f5003#)

The calendar part of this bug will be investigated later nearer the time 64 bit builds may be rolled out officially. At the moment, Lightning may be moving to jsical which would remove the need for individual binary builders.

Therefore this bug is a mixture of fixed/wontfix/invalid, so I'll pick invalid as it isn't completely fixed, nor is it completely wontfix.