You are browsing a read-only backup copy of Wikitech. The primary site can be found at wikitech.wikimedia.org

Phabricator/Deployment: Difference between revisions

From Wikitech-static
Jump to navigation Jump to search
imported>Brennen Bearnes
(→‎Initial setup: Link dev env notes)
 
imported>Hashar
mNo edit summary
Line 9: Line 9:
You'll need:
You'll need:


* A checkout of https://gerrit.wikimedia.org/r/plugins/gitiles/phabricator/deployment/ and all submodules.
* A checkout of https://gerrit.wikimedia.org/g/phabricator/deployment/ and all submodules.
* A local install of PHP 7.3.
* A local install of PHP 7.3.
* A running Phabricator install
* A running Phabricator install
Line 19: Line 19:


* scripts for tagging and pushing
* scripts for tagging and pushing
* ./scripts/tag-release.sh
* <code>./scripts/tag-release.sh</code>
** tags all submodules
** tags all submodules
** outputs markup for milestone (but this sometimes fails)
** outputs markup for milestone (but this sometimes fails)
** make sure everything got pushed
** makes sure everything got pushed


=== On phab1001 ===
=== On phab1001 ===
Line 36: Line 36:
** checks out the version
** checks out the version
** stops apache and php
** stops apache and php
** /usr/local/sbin/phab_deploy_finalize does db migrations and stuff
** <code>/usr/local/sbin/phab_deploy_finalize</code> does db migrations and stuff
* In {{irc|wikimedia-operations}}: <code>!log starting phabricator deploy, momentary downtime expected while apache restarts</code>
* In {{irc|wikimedia-operations}}: <code>!log starting phabricator deploy, momentary downtime expected while Apache restarts</code>
* <code>sudo ~/update.sh</code> and hope for best
* <code>sudo ~/update.sh</code> and hope for best
* <code>systemctl status phd</code> to make sure that's running
* <code>systemctl status phd</code> to make sure that's running
* <code>tail /var/log/phd.log</code> to check for problems
* <code>tail /var/log/phd/daemon.log</code> to check for problems
** always a lot of errors in here because of repo syncing, etc.
** always a lot of errors in here because of repo syncing, etc.
* check /var/log/apache2/phabricator.log
* check <code>/var/log/apache2/phabricator.log</code>


== Make milestone ==
== Make milestone ==

Revision as of 22:23, 4 June 2022

Deployment windows

Except for emergencies, Phabricator deployments should be conducted during mw:Phabricator/Maintenance windows.

Initial setup

You'll need:

Tagging a release

On your development system

  • scripts for tagging and pushing
  • ./scripts/tag-release.sh
    • tags all submodules
    • outputs markup for milestone (but this sometimes fails)
    • makes sure everything got pushed

On phab1001

  • /srv/phab
  • make sure it can pull
  • fetch all submodules on prod
  • ends at detached HEAD state
  • make sure tags are there
  • update.sh in mukunda's homedir on phab1001
    • puppet disable
    • stops phd
    • checks out the version
    • stops apache and php
    • /usr/local/sbin/phab_deploy_finalize does db migrations and stuff
  • In #wikimedia-operations connect: !log starting phabricator deploy, momentary downtime expected while Apache restarts
  • sudo ~/update.sh and hope for best
  • systemctl status phd to make sure that's running
  • tail /var/log/phd/daemon.log to check for problems
    • always a lot of errors in here because of repo syncing, etc.
  • check /var/log/apache2/phabricator.log

Make milestone

  • Go into phab project and rename "next" milestone to the date of the deploy
    • i.e. 2020-02-13
    • paste generated markup with stuff from release
    • create a new "next" milestone
      • "This is for tasks ... next phabricator update"
    • mukunda's script used to do this automatically, may need some updating
    • archive the old one