Releases/Firefox 21.0/BuildNotes: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 54: Line 54:


=== Things to undo ===
=== Things to undo ===
Due to the 'run build2 while build1 not actually dead' situation there are some things we need to undo
Due to the 'run build2 while build1 not actually dead' situation there are some things we need to undo:
* repush 21.0build1 snippets after build2 are generated
* repush 21.0build1 snippets after build2 are generated


If we end up shipping build1
<br>If we end up shipping build1:
* undo release config change and ensure reconfig before running any builders on build1
* undo release config change and ensure reconfig before running any builders on build1
* move FIREFOX_21_0_RELEASE tag back on to revision 3402fc52312c
* move FIREFOX_21_0_RELEASE tag back on to revision 3402fc52312c

Revision as of 09:55, 8 May 2013

Summary

Build 1

Checklist

Notes

  • merge from mozilla-beta, l10n milestone creation, and ship it submission done by bajaj. Review done by nthomas.
  • xulrunner checksums and push_to_mirrors jobs hit hg server errors when cloning the tools repo. The automation retried them successfully

Recover from full signing server disk

(bhearsum)
signing3's disk filled up (bug 869401) and failed the win32 build and many linux repacks. After the server was fixed, I did the following to recover:

  • Rebuilt the win32 build (failed to upload symbols, bug 869522, second rebuild was green)
  • Used the standalone builder to run the failed repacks for Linux (br bs ca cs csb et eu fa ff mai mk ml mr nb-NO si sk sl vi zh-CN zu) and Linux64 (bn-BD bn-IN bs ca cs es-ES es-MX et eu fa ff hr hu hy-AM id is it lt lv mai mk ml nb-NO rm ro ru si sk sl)
  • Once the standalone builders completed, ran "repack complete" builders with force build to get the automation unstuck.

Build 2

This is a straight rebuild of the same revision as build1 for the AMD crasher problem. We may not ship it, and builds are hidden from the general public to avoid confusion & diluting feedback on build1.

Checklist

Notes

  • ship it submission done by bajaj
  • review done by nthomas: moved from same revision as build1 to using the same relbranch (GECKO210_2013050704_RELBRANCH)
  • xulrunner push_to_mirrors failed because build1 had already been pushed, this is no problem

Things to undo

Due to the 'run build2 while build1 not actually dead' situation there are some things we need to undo:

  • repush 21.0build1 snippets after build2 are generated


If we end up shipping build1:

  • undo release config change and ensure reconfig before running any builders on build1
  • move FIREFOX_21_0_RELEASE tag back on to revision 3402fc52312c