Releases/Firefox 38.0.5/BuildNotes: Difference between revisions

Line 31: Line 31:
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".
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. This _should_ bump the necessary configs, update balrog, run update verify, etc. I don't have full confidence that this will actually work, but at the very least it's a starting point, and better than trying to bump everything by hand.
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


Current status: waiting for review on release config patch and this strategy.
After the updates builder ran the downstreams (update verify, ready for cdntest, etc.) seemed to fire correctly.
canmove, Confirmed users
6,439

edits