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>Hashar
mNo edit summary
imported>Brennen Bearnes
Line 18: Line 18:
=== On your development system ===
=== On your development system ===


* scripts for tagging and pushing
* Scripts for tagging and pushing
* <code>./scripts/tag-release.sh</code>
* <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)
** makes sure everything got pushed
** Makes sure everything got pushed
 
For celerity updates:
 
* https://secure.phabricator.com/book/phabcontrib/article/adding_new_css_and_js/
** The dependency and packaging maps are generated by bin/celerity map, which updates resources/celerity/map.php.


=== On phab1001 ===
=== On phab1001 ===


* /srv/phab
* /srv/phab is a clone of the deployment repo
* make sure it can pull
* Make sure it can pull
* fetch all submodules on prod
* Fetch all submodules on prod
* ends at detached HEAD state
* Ends at detached HEAD state
* make sure tags are there
* Make sure tags are there
* <code>update.sh</code> in mukunda's homedir on phab1001
* <code>update.sh</code> in mukunda's homedir on phab1001
** puppet disable
** puppet disable
Line 41: Line 46:
* <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/daemon.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 <code>/var/log/apache2/phabricator.log</code>
* Check <code>/var/log/apache2/phabricator.log</code>


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

Revision as of 18:02, 7 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

For celerity updates:

On phab1001

  • /srv/phab is a clone of the deployment repo
  • 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