Confirmed users
514
edits
Phabricator/UpgradeProcess: Difference between revisions
m
added info about version-control-tools directory
m (fixed typo and the command to run demo shell) |
m (added info about version-control-tools directory) |
||
| Line 35: | Line 35: | ||
3. The upgrade mechanic performs a simple smoke test: start up the phabricator.test container and log in, post a revision, accept the revision, verify that the attachment is created and r+ed in BMO. | 3. The upgrade mechanic performs a simple smoke test: start up the phabricator.test container and log in, post a revision, accept the revision, verify that the attachment is created and r+ed in BMO. | ||
* To run arc commands the upgrade mechanic can use the shell container: `docker-compose run demo` | * To run arc commands the upgrade mechanic can use the shell container: `docker-compose run demo`. There is a `version-control-tools` repo configured to run with demo phabricator. | ||
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. | ||