Release:Release Automation on Mercurial:Troubleshooting: Difference between revisions

Release:Release Automation on Mercurial:Troubleshooting (view source)

409 bytes removed , 17 July 2012

canmove, Confirmed users

6,441

edits

@@ Line 10: / Line 10: @@
 === Restarting failed builders without patching the config ===
-It's often easier to use Force Build or buildbot sendchange to restart specific things than it is to patch the configs, check in, update the master, etc. If you need to restart tag, source, an en-US build, l10nverify, updates, or update_verify you can use "Force Build" from the Buildbot waterfall.
+Most builders can be safely rebuilt with the "rebuild" button. Individual locales can be triggered through the [[Release:Release_Automation_on_Mercurial:Tagging_through_Signing#Standalone_Repack_Builders | standalone repack builders]]. Ask someone if you don't know if it's safe to restart something or not.
-If you need to restart a single l10n build (that is, one locale) on a single platform you may also use "Force Build", but be sure to use en_revision, l10n_revision, and locale as properties. The revision properties should be set to _RELEASE tags, and the locale should be obvious.
-If you need to restart many or all locales you'll have to fill out the web interface multiple times, until {{bug|518589}} is resolved.
 === Restarting a builder from a certain point ===