Confirmed users
3,376
edits
ReleaseEngineering/How To/Deploy A New OS Image: Difference between revisions
ReleaseEngineering/How To/Deploy A New OS Image (view source)
Revision as of 18:26, 22 February 2019
, 22 February 2019polish
(update) |
(polish) |
||
| Line 6: | Line 6: | ||
With the exception of Linux and Android emulators, all the other operating systems require changes out of the mozilla-central tree that will affect all branches. | With the exception of Linux and Android emulators, all the other operating systems require changes out of the mozilla-central tree that will affect all branches. | ||
This document assumes you have already created a small pool of test machines and proven a reliable installation technique. This document also assumes that you have | This document assumes you have already created a small pool of test machines and proven a reliable installation technique. This document also assumes that you have [https://wiki.mozilla.org/index.php?title=ReleaseEngineering/How_To/Validate_a_New_Config validated the new image]. | ||
Given a try push that shows a green run (green can include intermittents) we will follow these steps: | Given a try push that shows a green run (green can include intermittents) we will follow these steps: | ||
* contact Release Management: release-mgmt@mozilla... and the sheriffs: sheriffs@mozilla... to let the know the intent to upgrade. | |||
* choose a date that is ideally 1-2 weeks prior to the next [https://wiki.mozilla.org/RapidRelease/Calendar merge date] | |||
* schedule a short meeting to make sure there is a contact from relman, CI, relops, sheriffs to work with until this is resolved, also to ensure all questions about testing, timing, impact are surfaced. | |||
* address concerns as needed and do more complete testing (in this case on all branches that are affected such as mozilla-beta, mozilla-release, mozilla-esr*) with patches to green up each branch respectively. | |||
* communicate to stakeholders when all done testing to confirm the date | |||
* check in with stakeholders 2 business days before the planned deploy in case there is an emergency or change of plans | |||
** if we need to change the date, prepare to retest all patches/branches | |||
* after the deployment, followup with a summary to indicate the work is done and what surprises were found | |||