Closed Bug 869974 Opened 12 years ago Closed 11 years ago

Install MAPI headers on the Windows builders for Thunderbird (needed for Gecko 24)

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

All
Windows 7
task
Not set
blocker

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: standard8, Assigned: jhopkins)

References

Details

In bug 869966 I am looking at getting the Thunderbird builds moved onto the Windows 8 SDK. As part of this, bug 789787 comment 0 says we need the MAPI headers installing separately, they are available here: https://connect.microsoft.com/VisualStudio/feedback/details/728601/visual-c-mapiutil-h-and-xcmc-h-are-missing-from-platform-sdk-included-with-vc11-beta
Blocks: 869966
I've a patch on bug 869966 which enables the Windows 8 SDK for Thunderbird (but obviously fails on try). I suspect it'll need an INCLUDE change once we install the headers... ... so maybe we could try this on a staging box first?
This is now a blocker for Thunderbird on Aurora/Central, as the builds are red due to the fact the builders have got the win8sdk installed, but are using the previous SDK. Whilst we can possibly work around it by disabling MAPI (I haven't tried yet), I don't think we want to head to release with MAPI disabled without an alternative. I also think we should be using the same sdk as FF in case of issues, and I've been a bit lax in getting this requirement updated.
Severity: normal → blocker
Flags: needinfo?(coop)
Mark: do you need a staging box to figure this out (based on comment #1)? Is that the ask here?
Flags: needinfo?(coop)
Coop: I think trying a build on staging with these headers included would be good as a first step, but pretty quickly after that, we're going to want these deployed to all builders.
Summary: Install MAPI headers on the Windows builders for Thunderbird → Install MAPI headers on the Windows builders for Thunderbird (needed for Gecko 24)
(In reply to Mark Banner (:standard8) from comment #4) > Coop: I think trying a build on staging with these headers included would be > good as a first step, but pretty quickly after that, we're going to want > these deployed to all builders. Mark I can get you a build machine loaned over on monday if you'd like... which you can then install the MAPI headers and test, and report back on what needs doing. Can you get a seperate loaner bug on file for me to do that?
Flags: needinfo?(mbanner)
I'm not going to have too much time to play around over the next few days, so it would be useful if someone from releng could do the setup. What would be the ETA on that? If its too long, I might be able to find some time, but I can't guarantee that.
Flags: needinfo?(mbanner)
Assignee: nobody → jhopkins
Depends on: 891363
Headers installed on w64-ix-slave22 to the default location of: C:\Office 2010 Developer Resources\Outlook 2010 MAPI Headers Downloaded from: http://www.microsoft.com/en-us/download/details.aspx?id=12905 (direct link: http://download.microsoft.com/download/B/6/4/B645F2C9-715A-4EAB-B561-CC0C9779C249/Outlook2010MAPIHeaders.EXE)
I've been trying the builder, and I can get it to build fine with the headers installed. There's a minor mozconfig change required, that I'll handle in bug 869966. Apart from that, I think this is fine to be rolled out to all the builders.
Rolling out MAPI headers to the w64 build slaves now.
MAPI headers copied to all the w64 build slaves.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.