canmove, Confirmed users
6,439
edits
Balrog: Difference between revisions
→Baking in stage
| Line 108: | Line 108: | ||
To get the new code in stage you must create a new Release in Github as follows: | To get the new code in stage you must create a new Release in Github as follows: | ||
# Tag the repository with a "vX.Y" tag. Eg: "git tag -s vX.Y && git push --tags" | # Tag the repository with a "vX.Y" tag. Eg: "git tag -s vX.Y && git push --tags" | ||
# Diff against the previous release tag. Eg: "git diff v2.24 v2.25" | # 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 deploy them to stage. It may take upwards of 30 minutes for the deployment to happen. | # [https://github.com/mozilla/balrog/releases Create a new Release on Github]. This create new Docker images tagged with your version, and deploy them to stage. It may take upwards of 30 minutes for the deployment to happen. | ||