Content translation/Deployments/How-to

Jump to navigation Jump to search

This document describes deployment procedure for ContentTranslation, cxserver and Apertium.


Content Translation is updated via regular MediaWiki train. In case of manual update needed, follow the steps below.

  1. Update desired branches to desired commit/update using delete and create branches at Gerrit interface,,branches In case of emergency, note down old hash.
  2. Read and follow: Make sure you've clean copy of MediaWiki/core for this.
  3. You're ready for actual deployment.



Note down image tag version from Gerrit patchset to be deploy. For eg: has 2019-04-11-112002-production tag.

ssh deploy1001
cd /srv/scap-helm/cxserver/

Edit: cxserver-*-values.yaml with new version.


CLUSTER=codfw scap-helm cxserver status production


CLUSTER=codfw scap-helm cxserver status upgrade -f cxserver-codfw-values.yaml production stable/cxserver
CLUSTER=eqiad scap-helm cxserver status upgrade -f cxserver-eqiad-values.yaml production stable/cxserver
CLUSTER=staging scap-helm cxserver status upgrade -f cxserver-staging-values.yaml staging stable/cxserver


CLUSTER=codfw scap-helm cxserver status history


To rollback to particular revision:

CLUSTER=codfw scap-helm cxserver status rollback production <REV>

See also[edit]


Apertium deployment is done via updating apertium packages through Gerrit change and puppet.


  1. Check if package list are up-to-date in Puppet.
  2. Make sure to ask to restart 'apertium-apy' on scb1001 and scb1002 to any Ops member after adding new languages support for Apertium MT.
  3. Check logs at: /srv/logs/apertium/

See also[edit]

  1. Apertium packaging and service information: