462515 - move fx-linux-1.9-slave4 and fx-win32-1.9-slave4 to production-1.9-master

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[[e-mail] (:bhearsum)]

In order to be able to run releases without stopping l10n builds we should move these slaves over to the production 1.9 master. After this, we'd still only have one Mac on that master - but it should be able to handle the load by itself.

Comment 1

[Armen [:armenzg]]

I haven't had time to work on this, putting back into the pool

Comment 2

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

I'd like us to do some checks of fx-linux-1.9-slave1/2 (staging/production) compared to 3/4 (newer unused slaves). They were cloned at different times and may have diverged.

Comment 3

[Chris AtLee [:catlee]]

all of fx-linux-slave{1,2,3,4} are active.  1,3,4 are currently in staging, and 2 is in production.

Comment 4

[Chris AtLee [:catlee]]

Attachment: Add fx-linux-1.9-slave4 and fx-win32-1.9-slave4 to production-1.9

Comment 5

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

Comment on attachment 360770 [details] [diff] [review]
Add fx-linux-1.9-slave4 and fx-win32-1.9-slave4 to production-1.9

Is there a corresponding patch coming for staging-1.9?

Comment 6

[Chris AtLee [:catlee]]

Comment on attachment 360770 [details] [diff] [review]
Add fx-linux-1.9-slave4 and fx-win32-1.9-slave4 to production-1.9

Checking in production-1.9/master.cfg;
/cvsroot/mozilla/tools/buildbot-configs/automation/production-1.9/master.cfg,v  <--  master.cfg
new revision: 1.42; previous revision: 1.41
done

Comment 7

[Chris AtLee [:catlee]]

These two slaves are now running on production, waiting for new builds.

Comment 8

[Chris AtLee [:catlee]]

New builds on slaves look good.