Balrog: Difference between revisions

Balrog (view source)

96 bytes removed , 12 September 2017

→‎Pushing to production: update production verification instructions

canmove, Confirmed users

6,441

edits

@@ Line 81: / Line 81: @@
 #* Wednesdays are usually the best day to push to production, because they are generally free of release events. Unless you have a specific need to deploy on a different day, you should request the prod push for a Wednesday.
 #* You should link any bugs being deployed is the "Blocks" field.
-# Once the push has happened, verify the changes in production. If you need to tweak rules or releases to do so, be careful not to touch any live channels (create new rules or releases if necessary). This final verification is as more about making sure the right thing got deployed than whether or not your code is correct.
+# Once the push has happened, verify that the code was pushed to production by checking the __version__ endpoints on [https://aus4-admin.mozilla.org/__version__ the Admin] and [https://aus5.mozilla.org/__version__ Public] apps.
 # Bump the [https://github.com/mozilla/balrog/blob/master/version.txt in-repo version] to the next available one to ensure the next push gets a new version.