Coop

Community tinderbox migration update: VM migrations start tomorrow

Posted 1 year, 7 months ago at 17:00. 1 comment

As a quick synopsis for those not directly involved in what has been going on, the Mozilla build team (with lots of help from the IT team) is moving all of the tinderboxen for community project builds — Camino, SeaMonkey, and Sunbird/Lightning, — onto a separate build network. Build engineers for those products will then have direct access to those build environments for configuration maintenance and debugging. This will resolve a longstanding complaint from community developers about turnaround time for tinderbox requests by allowing/forcing them to fix things themselves. Be careful what you wish for, people!

Honestly though, we think this will be a boon for everyone. Yes, it will hopefully mean less time spent mucking with random tinderboxen for us, but it will also allow community projects to determine their own build system destiny, while still being able to take advantage of the existing Mozilla build infrastructure for things like automated configuration updates if they so choose.

And now, the update: mrz is going to start migrating VMs used by Mozilla community projects onto their own VM host tomorrow (Wednesday). We’re hoping to bang them all out in one go, but we’ll continue Thursday and Friday evening if necessary. The practical fallout from this is that Mozilla-hosted Linux and Windows builds for community projects may/will have some downtime tomorrow, but it will be after the nightlies are generated and any given build should only be offline for a few hours at most.