Confirmed users
514
edits
Phabricator/UpgradeProcess: Difference between revisions
Jump to navigation
Jump to search
m
added an info about pushing to the master repo
m (added an info that a mozphab repo needs to be commited) |
m (added an info about pushing to the master repo) |
||
| Line 37: | Line 37: | ||
4. If the smoke test fails, the mechanic files bugs as appropriate. At the next standup, determine the priority of these fixes and if they should fit into the current sprint, or if the upgrade should be delayed to the next sprint. | 4. If the smoke test fails, the mechanic files bugs as appropriate. At the next standup, determine the priority of these fixes and if they should fit into the current sprint, or if the upgrade should be delayed to the next sprint. | ||
5. If the tests pass immediately, or if the bugs are fixed and the tests then pass, commit the mozphab with updated hash and file a bug under Conduit :: Infrastructure noting the new hash. | 5. If the tests pass immediately, or if the bugs are fixed and the tests then pass, commit the mozphab with updated hash, push to master branch, and file a bug under Conduit :: Infrastructure noting the new hash. | ||
6. On the following Tuesday, operations will deploy to dev. The upgrade mechanic should do the same simple smoke test on the dev system. | 6. On the following Tuesday, operations will deploy to dev. The upgrade mechanic should do the same simple smoke test on the dev system. | ||