Release:Release Automation on Mercurial:Starting a Release: Difference between revisions

Release:Release Automation on Mercurial:Starting a Release (view source)

79 bytes added , 20 June 2012

Confirmed users

4,293

edits

@@ Line 43: / Line 43: @@
 = Locking slaves =
-Because releases happen on only one master and slaves are scattered across all of them, it's necessary to make sure you have enough slaves to complete the release in a timely manner prior to starting. Generally, you need at least 3 or 4 for each platform you build on. Use the Buildbot interface for each build platform (eg, http://buildbot-master12.build.scl1.mozilla.com:8001/builders/release-mozilla-release-win32_build) and verify that you have them. If you don't have enough use [http://slavealloc.build.mozilla.org/ui/#slaves Slavealloc] to lock additional slaves to your master. If you don't know how to do this, ask someone.
+Because releases happen on only one master and slaves are scattered across all of them, it's necessary to make sure you have enough slaves to complete the release in a timely manner prior to starting. Generally, you need at least 3 or 4 for each platform you build on, but 6 is necessary to fully parallelize l10n repacks for minimum time elapsed. Use the Buildbot interface for each build platform (eg, http://buildbot-master12.build.scl1.mozilla.com:8001/builders/release-mozilla-release-win32_build) and verify that you have them. If you don't have enough use [http://slavealloc.build.mozilla.org/ui/#slaves Slavealloc] to lock additional slaves to your master. If you don't know how to do this, ask someone.
 = Setting reserved slaves =