canmove, Confirmed users
6,441
edits
Balrog: Difference between revisions
→Baking in stage
| Line 110: | Line 110: | ||
# Diff against the previous release tag. Eg: "git diff v2.24 v2.25", to double whether or not there's schema changes. | # Diff against the previous release tag. Eg: "git diff v2.24 v2.25", to double whether or not there's schema changes. | ||
#* Look for anything unexpected, or any '''schema changes'''. If schema changes are present, see the above section for instructions on handling them. | #* Look for anything unexpected, or any '''schema changes'''. If schema changes are present, see the above section for instructions on handling them. | ||
# [https://github.com/mozilla/balrog/releases Create a new Release on Github]. This create new Docker images tagged with your version, and | # [https://github.com/mozilla/balrog/releases Create a new Release on Github]. This create new Docker images tagged with your version, and deploys them to stage. It may take upwards of 30 minutes for the deployment to happen. | ||
Once the changes are deployed to stage, let them bake for at least 24 hours. You can do additional targeted testing here if you wish, or simply wait for nightlies/releases to prod things along. It's a good idea to watch Sentry for new exceptions that may show up, and Datadog for any notable changes in the shape of the traffic. | Once the changes are deployed to stage, let them bake for at least 24 hours. You can do additional targeted testing here if you wish, or simply wait for nightlies/releases to prod things along. It's a good idea to watch Sentry for new exceptions that may show up, and Datadog for any notable changes in the shape of the traffic. | ||