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

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

692 bytes removed , 19 August 2015

canmove, Confirmed users

6,441

edits

@@ Line 23: / Line 23: @@
 You can confirm disk space is the issue via browsing [https://graphite-scl3.mozilla.org/dashboard/ graphite].
-=== Restarting the automation from a specific point ===
-The automation has the ability to easily skip tagging, source generation, or en-US builds in the event that you want to restart from source, en-US, or l10n repacks. To make use of this, you need to add skip_$builder flags to the release config. For example, to restart from l10n repacks you will need to add the following lines to the release config:
- releaseConfig['skip_tag'] = 1
- releaseConfig['skip_source'] = 1
- releaseConfig['skip_build'] = 1
-Only these three steps (and repo_setup, if you're in staging) are skippable. If you need to restart in later parts of the automation, "Force Build" is the supported method of doing so.
 === Restarting failed builders without patching the config ===