467833 - Turn off bsmedberg's mozilla-central l10n machines

Status: RESOLVED FIXED

(Release Engineering :: General, defect, P2)

Description

[Chris Cooper [:coop] (he/him)]

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.

Comment 1

[Axel Hecht [:Pike]]

bsmedberg's builds are building on push, marking the a dependency on bug 464163.

Comment 2

[Armen [:armenzg]]

Just removing blocking bug 464164 since resolving this bug is not blocking the l10n nightly builds for mozilla-1.9.1 from being fixed.

Comment 3

[Nick Thomas [:nthomas] (UTC+12)]

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.

Comment 4

[Chris Cooper [:coop] (he/him)]

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.

Comment 5

[Chris Cooper [:coop] (he/him)]

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.

Comment 6

[Axel Hecht [:Pike]]

buildbot stop slavedir, too, I guess?