Releases/Firefox 38.0.5/BuildNotes

From MozillaWiki
Jump to navigation Jump to search

Checklist

Build 1

Failed before it started because the production-0.8 branch of buildbotcustom was busted for non-release reasons. bhearsum backed out the bustage and started build2.

Build 2

Issues starting because the release-runner reconfig conflicted with the hourly reconfig, so that the two schedulers on bm81 as well as bm71 and bm74 were not reconfiged by release runner. eg

[FAIL] lockfile (reconfig.lock) found in buildbot-master81.bb.releng.scl3.mozilla.com:/builds/buildbot/build_scheduler

When the sendchange was sent we got this in the build_scheduler:

 2015-05-21 14:01:41-0700 [Broker,46296,10.26.68.33] FIREFOX_38_0_1_RELEASE revision does not match script_repo_revision FIREFOX_38_0_5_RELEASE

bug 1167467 for these issues. Recovered by reconfiging the 4 affected masters, and re-doing the sendchange.

Cancelled in tagging, because the branding and update config was not set up properly. We need to backout 27bacb9dff64 for build3. Done in 79f9cd31b4b1.

Build 3

Deal with missing beta channel updates

KaiRo noticed that 38.0.5 didn't become available on beta-cdntest. This is because we only enable the beta channel for "final" releases (http://mxr.mozilla.org/build/source/tools/buildfarm/release/release-runner.py#145), which means "two digit version number".

Our assumption was broken by 38.0.5, so this never happened. I _think_ the best way to fix this up is to tweak the release config by hand, retag, reconfig, and then kick the beta updates builder. I landed https://bugzilla.mozilla.org/attachment.cgi?id=8609368&action=edit to enable all the necessary builders and reconfiged the build and scheduler masters for it. After that was done, I:

  • Reran bouncer submitter to add necessary bouncer entries with force bulid
  • Ran beta updates builder with force build

After the updates builder ran the downstreams (update verify, ready for cdntest, etc.) seemed to fire correctly.