Page MenuHomePhabricator

Establish a merge and deploy workflow for wikimedia/portals repository
Closed, ResolvedPublic



  • there is no wmf/ branch for this repository, only a master branch
  • there is no way only cloning the wikimedia/portals repository to know what's deployed
  • the operations/mediawiki-config contains a submodule entry for wikimedia/portals

Problem is we need to query information from one repo to know what's currently deployed on the servers.

This is peculiar: for any other config repo, the master or production branch for puppet is what's deployed, for any code repo, the wmf branch is what's deployed.

I suggest we devise how to fix that. Some solutions:

  • Don't merge before deployment, probably the easiest
  • Add a wmf branch we can rebase to last deployed version
  • Tag last deployed version with "production" Git tag

Event Timeline

Restricted Application added a project: Discovery. · View Herald TranscriptMay 25 2016, 12:17 PM
Restricted Application added subscribers: Zppix, Aklapper. · View Herald Transcript
Dereckson renamed this task from Establish a merge and deploy workflow to Establish a merge and deploy workflow for wikimedia/portals repository.May 25 2016, 12:18 PM
Dereckson added a subscriber: JGirault.
Jdrewniak closed this task as Resolved.Aug 31 2018, 2:38 PM
Jdrewniak claimed this task.

Closing this out since in late 2017 we created a "deploy" repo for the Portals project, which contains only the build assets. The builds are generated and deployed weekly. This ensures that each commit represents a new deploy, so rolling back just means reverting the last commit in that repo. More details in T180777 .