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

Line 31: Line 31:


=== Re-spinning a single locale ===
=== Re-spinning a single locale ===
'''WARNING: These instructions are extremely out of date. Consider them nothing more than a vague guideline. Please think through this yourself if you need to do it.'''
We sometimes run into the case where individual locales need to be re-spun. Some reasons this might happen include network timeouts or build slave failures. When this happens, you can follow the following steps to recover and re-spin the missing locale(s):
We sometimes run into the case where individual locales need to be re-spun. Some reasons this might happen include network timeouts or build slave failures. When this happens, you can follow the following steps to recover and re-spin the missing locale(s):
# Manually re-tag the locale's repository (if necessary). You can find the appropriate revision to use for tagging from the shipped-locales file, or from the [https://l10n-stage-sj.mozilla.org/shipping/milestones l10n shipping dashboard]
# Manually re-tag the locale's repository (if necessary). You can find the appropriate revision to use for tagging from the shipped-locales file, or from the [https://l10n-stage-sj.mozilla.org/shipping/milestones l10n shipping dashboard]
canmove, Confirmed users
6,441

edits