Once we are generating l10n builds for mozilla-central using Armen's code (bug 460791), we need to retire bsmedberg's machines, or at the very least change where they upload their builds to avoid collisions/overwrites.
Just removing blocking bug 464164 since resolving this bug is not blocking the l10n nightly builds for mozilla-1.9.1 from being fixed.
No longer blocks: 464164
Both systems are pushing into firefox/nightly/latest-mozilla-central-l10n/ at the moment, and some of the permissions there were very wonky (eg 331) and I've reset them to 664 for files, 775 for the *-xpi dirs. I noted that xpi's are being published to different locations by the two systems.
I'm about to enable repack-on-change for 1.9.1 on the releng pool of build slaves. I'm not turning these machines off immediately, but they are now sending builds to firefox/nightly/experimental/latest-mozilla-1.9.1-l10n (was previously not going to experimental). For continuity, Tinderbox notifications will continue to go to Mozilla-l10n until we disable these builders entirely.
Status: NEW → ASSIGNED
Priority: P3 → P2
With bug 464165 fixed, we can finally turn these off. I just shutdown the master. We won't repurpose the VMs/machines yet just to be safe.
buildbot stop slavedir, too, I guess?
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.