Releases/Firefox 21.0/BuildNotes: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 81: Line 81:
* xulrunner push_to_mirrors failed because build1 had already been pushed
* xulrunner push_to_mirrors failed because build1 had already been pushed
** removed /pub/mozilla.org/xulrunner/releases/21.0 as xrbld@stage, then rebuilt
** removed /pub/mozilla.org/xulrunner/releases/21.0 as xrbld@stage, then rebuilt
* QA automation expects there to be N directories if you're up to buildN, but we have hidden build2. Created empty dir at .../21.0-candidates/build2-for-qa-automation/ to work around this.
<i>


<i>
= Build 4 (Desktop) =
= Build 4 (Desktop) =
'''May''' do this for AMD crash issue.
'''May''' do this for AMD crash issue.

Revision as of 01:44, 12 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 (Desktop)

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 had to undo:

  • repush 21.0build1 snippets after build2 are generated (QA had some issues with this until we repushed build1)


If we end up shipping build1:

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

Build 2 (Android)

Code change resolving regression from bug 853522

Checklist

Notes

  • bajaj submitted, nthomas review, no issues

Build 3 (Desktop)

This is a new build to address several bugs.

Checklist

Notes

  • xulrunner push_to_mirrors failed because build1 had already been pushed
    • removed /pub/mozilla.org/xulrunner/releases/21.0 as xrbld@stage, then rebuilt
  • QA automation expects there to be N directories if you're up to buildN, but we have hidden build2. Created empty dir at .../21.0-candidates/build2-for-qa-automation/ to work around this.

Build 4 (Desktop)

May do this for AMD crash issue.

Notes

Things to undo

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

  • repush 21.0build3 snippets after build4 are generated (QA had some issues with this until we repushed build1)


If we end up shipping build3 instead of build4:

  • undo release config change, move FIREFOX_21_0_RELEASE tag back, and ensure reconfig before running any builders for build3
  • move FIREFOX_21_0_RELEASE tag back to FIREFOX_21_0_BUILD3 on mozilla-release, plus build repos (except buildbot-configs done above)
  • move FIREFOX_21_0_RELEASE_RUNTIME tag in tools repo to position of FIREFOX_21_0_BUILD3_RUNTIME
    • to revision for build3
    • tools, , buildbotcustom repos