canmove, Confirmed users
6,442
edits
Balrog: Difference between revisions
Jump to navigation
Jump to search
→Pushing to production
| Line 120: | Line 120: | ||
#* 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 | #* 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. | #* You should link any bugs being deployed is the "Blocks" field. | ||
#* Make sure you substitute the version number and choose the correct | #* Make sure you substitute the version number and choose the correct options from the bug template. | ||
# 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. | # 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. | # 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. | ||