Closed Bug 764939 Opened 12 years ago Closed 12 years ago

[calendar] Switch win32 build slaves to Visual C++ 2010

Categories

(Calendar :: Build Config, defect)

x86
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: ssitter, Assigned: Fallen)

References

Details

Now that Visual C++ 2010 is available on the win32 build slaves (Bug 757500) we should switch the build to actually use it. Any ideas what needs to be done for this? Maybe a patch similar to the one in Thunderbird Bug 751592?
Yes, something like that should be the right step. I'll make sure to reconfigure buildbot this afternoon.
Assignee: nobody → philipp
The switch to vc10 was done for Thunderbird 15, therefore we need to switch both comm-aurora and comm-central builders. Maybe we can store the config files inside the source tree like done for Thunderbird, i.e. the builders correctly setup itself during the merge days?
(In reply to Philipp Kewisch [:Fallen] from comment #1)
> Yes, something like that should be the right step. I'll make sure to
> reconfigure buildbot this afternoon.

No need to reconfig buildbot for this, just check in the changes to the mozconfigs here:

http://hg.mozilla.org/build/buildbot-configs/file/d62b0ac0b092/calendar/win32
Status: NEW → ASSIGNED
build/buildbot-configs changeset b6a2f979f8c8
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
OS: Windows 7 → All
Hardware: x86 → All
Resolution: --- → FIXED
Target Milestone: --- → 1.7
OS: All → Windows 7
Hardware: All → x86
Blocks: 753456
We just need to remember to repeat the change for comm-beta and comm-release once Lightning 1.7 is merged to that branch.
Agreed. I'm not sure yet how we could get the mozconfigs into the tree. There surely will be code that loads the in-tree mozconfigs and we'd have to tell it to also load the calendar mozconfigs if --enable-calendar is passed. Since thats a mozconfig option itself, we'd need some other way to determine when to build calendar (environment var?). Maybe a new bug would be good for that.
You need to log in before you can comment on or make changes to this bug.