Confirmed users
514
edits
Phabricator/UpgradeProcess: Difference between revisions
Jump to navigation
Jump to search
Modified steps after smoke test
m (added an info about pushing to the master repo) |
(Modified steps after smoke test) |
||
| 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, | 5. If the tests pass immediately, or if the bugs are fixed and the tests then pass, commit the mozphab with updated hash, create the pull request. | ||
6. | 6. When the change is merged the new mozilla/mozphab image is built by circle ci and the new docker sha will be at https://hub.docker.com/r/mozilla/mozphab/tags/add. Add the new hash to phabricator-extension's Dockerfile, commit and create the revision in Phabricator. | ||
7 | 7 After landing the revision file a bug under Conduit :: Infrastructure noting the new hash. | ||
8. On | 8. On the following Tuesday, operations will deploy to dev. The upgrade mechanic should do the same simple smoke test on the dev system. | ||
9. | 9. On Wednesday (possibly the next week if there were bugs), operations deploys to stage and updates the bug, assigning it to QA (chartjes). | ||
10. If QA gives is a pass (in the bug), operations deploys to production on Thursday. Otherwise go to step 4. | 10. QA runs the bigger [[Phabricator/TestPlan|test plan]] against stage. ''At this time there are issues with stage caused by BMO stage being behind a VPN. We will use dev for QA's testing until this problem is solved.'' | ||
11. If QA gives is a pass (in the bug), operations deploys to production on Thursday. Otherwise go to step 4. | |||