Phabricator/UpgradeProcess: Difference between revisions

Phabricator/UpgradeProcess (view source)

Revision as of 21:54, 4 December 2017

113 bytes added , 4 December 2017

m

Moved shell container to an optional step

Zalun

Confirmed users

514

edits

@@ Line 23: / Line 23: @@
 * make sure you do not override this in `docker-compose.override.yml`
-.5. Run `docker-compose -f docker-compose.yml -f docker-compose.shell.yml run shell sh` in the `bmo-extensions` directory. This will spin up all containers with an additional one called shell with arc installed.
+.5. Run `docker-compose up --build` in the `bmo-extensions` directory. This will spin up all containers with an additional one called shell with arc installed.
 .6. Make sure that the you configure your Firefox proxy to use the tinyproxy started on docker-ip:1090.
@@ Line 31: / Line 31: @@
 .8 Upgrade database: SSH into bmo-extensions' phabricator (`docker exec -it bmoextensions_phabricator_1 /bin/sh`), run db migration: `phabricator/ $ ./bin/storage upgrade`
-. The upgrade mechanic performs a simple smoke test: start up the demo container and log in, post a revision, accept the revision, verify that the attachment is created and r+ed in BMO.
+. 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 -f docker-compose.yml -f docker-compose.shell.yml run shell sh`
 . 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.