Canmove, confirm
6,438
edits
Changes
→Pushing to production
=== Pushing to production ===
Pushing live requires CloudOps. For non-urgent pushes, you should begin this procedure a few hours in advance to give CloudOps time to notice and respond. For urgent pushes, file the bug immediately and [https://mana.mozilla.org/wiki/display/SVCOPS/Contacting+Cloud+Operations escalate if no action is taken quickly]. Either way, you must follow this procedure to push:
# [https://bugzilla.mozilla.org/enter_bug.cgi?assigned_to=dthorn%40mozilla.com&bug_file_loc=http%3A%2F%2F&bug_ignored=0&bug_severity=normal&bug_status=NEW&cc=dthorn%40mozilla.com&cc=miles%40milescrabill.com&cc=bhearsum%40mozilla.com&cf_blocking_fennec=---&cf_fx_iteration=---&cf_fx_points=---&cf_status_firefox56=---&cf_status_firefox57=---&cf_status_firefox58=---&cf_status_firefox_esr52=---&cf_tracking_firefox56=---&cf_tracking_firefox57=---&cf_tracking_firefox58=---&cf_tracking_firefox_esr52=---&cf_tracking_firefox_relnote=---&comment=Balrog%20version%20X.Y%20is%20ready%20to%20be%20pushed%20to%20prod.%20Please%20deploy%20the%20new%20Docker%20images%20%28vX.Y%29%20for%20admin%2C%20public%2C%20and%20the%20agent.%0D%0A%0D%0AWe%27d%20like%20the%20production%20push%20for%20this%20to%20happen%20sometime%20between%2011am%20and%201pm%20pacific%20on%20%28DATE%20GOES%20HERE%29.%0D%0A%0D%0AONE%20OF%3A%0D%0A%28NO%20SCHEMA%20CHANGE%20ADDITIVE29%20This%20release%20does%20not%20contain%20a%20schema%20change.%0D%0A%28ADDITIVE%20SCHEMA%20CHANGE%29%20This%20release%20requires%20a%20schema%20change%20that%20needs%20to%20be%20done%20_prior_%20to%20the%20new%20code%20going%20out.%20It%20can%20be%20performed%20by%20running%20the%20Docker%20image%20with%20the%20%22upgrade-db%22%20command%2C%20with%20DBURI%20set.%0D%0A%28DESTRUCTIVE%20SCHEMA%20CHANGE%29%20This%20release%20requires%20a%20schema%20change%20that%20needs%20to%20be%20done%20_after_%20to%20the%20new%20code%20is%20fully%20deployed.%20It%20can%20be%20performed%20by%20running%20the%20Docker%20image%20with%20the%20%22upgrade-db%22%20command%2C%20with%20DBURI%20set.%0D%0A%0D%0AONE%20OF%3A%0D%0A%28NO%20SCHEMA%20CHANGE%20OR%20ADDITIVE%20SCHEMA%20CHANGE%29%20If%20anything%20goes%20wrong%20with%20the%20new%20version%20in%20production%2C%20we%20can%20safely%20rollback.%0D%0A%28DESTRUCTIVE%20SCHEMA%20CHANGE%29%20If%20anything%20goes%20wrong%20with%20the%20new%20version%20in%20production%2C%20we%20must%20revert%20the%20schema%20change%20prior%20to%20rolling%20any%20code%20back%20by%20running%20the%20following%20command%20in%20the%20admin%20container%3A%0D%0Apython%20%2Fapp%2Fscripts%2Fmanage-db.py%20-d%20%24DBURI%20--version%20X%0D%0A%28UNABLE%20TO%20COME%20UP%20WITH%20SAFE%20ROLLBACK%20PROCEDURE%20-%20THIS%20SHOULD%20NEVER%20HAPPEN%29%20This%20push%20contains%20changes%20that%20cannot%20be%20safely%20rolled%20back.%20If%20anything%20goes%20wrong%20with%20the%20new%20version%20in%20production%2C%20please%20escalate%20to%20me.%0D%0A%0D%0AONE%20OF%3A%0D%0A%28NO%20NEW%20INTERDEPENDENT%20CODE%20BETWEEN%20admin%2Fpublic%2Fagent%29%20If%20anything%20goes%20wrong%20with%20one%20of%20the%20apps%2C%20it%20may%20be%20rolled%20back%20independently%20of%20the%20others.%0D%0A%28NEW%20CODE%20REQUIRES%20admin%2Fpublic%2Fagent%20ON%20THE%20MOST%20RECENT%20VERSION%29%20If%20anything%20goes%20wrong%20with%20just%20one%20of%20the%20apps%2C%20all%20of%20them%20must%20be%20rolled%20back.&component=Operations%3A%20Deployment%20Requests&contenttypemethod=autodetect&contenttypeselection=text%2Fplain&defined_groups=1&flag_type-37=X&flag_type-4=X&flag_type-5=X&flag_type-607=X&flag_type-708=X&flag_type-721=X&flag_type-737=X&flag_type-787=X&flag_type-800=X&flag_type-803=X&flag_type-846=X&flag_type-864=X&flag_type-914=X&flag_type-916=X&form_name=enter_bug&maketemplate=Remember%20values%20as%20bookmarkable%20template&op_sys=Unspecified&priority=--&product=Cloud%20Services&rep_platform=Unspecified&short_desc=please%20deploy%20balrog%20X.Y%20to%20prod&target_milestone=---&version=unspecified File a bug] to have the new version pushed to production.
#* Wednesdays between 11am and 1pm are usually the best day to push to production, because they are generally free of release events, nightlies, and cronjobs. Unless you have a specific need to deploy on a different day, you should request the prod push for a Wednesday between those hours
#* You should link any bugs being deployed is the "Blocks" field.
