Content translation/Deployments/Checklist

From MediaWiki.org
Jump to navigation Jump to search

This is checklist to follow before cxserver is deployed in Production:

cxserver[edit]

  1. All automated tests are passed.
  2. Test configuration in Labs/Beta.

CX1[edit]

  1. Check all endpoints: /v1?doc
  2. Start translation with CX1 from master with to be deployed cxserver. Test against patches going to be in production.

CX2[edit]

  1. Check all endpoints: /v2?doc

MT[edit]

Apertium[edit]

  1. Apertium package in Labs instance (language-apertium) OK? In case of new package, install it manually.
  2. Check if pair is single directional or bi-directional?
  3. Mapping is added in cxserver/lib/mt/Apertium.languagenames.json for new language.

External MTs[edit]

  1. Test with provided keys (if any).
  2. Check in dashboard (if any).
  3. Logstash log some errors for external MTs.

cxserver/deploy[edit]

  1. Patch for cxserver/deploy is built without any error. Default build system is Debian Jessie at moment. Note down any error(s) and follow up.
  2. When not intended, do not update node_modules (--force option)
  3. Patch is deployed in Beta and http://cxserver-beta.wmflabs.org/v1?doc and http://cxserver-beta.wmflabs.org/v2?doc end points are OK.
  4. No errors during deployment to canary. Else stop and revert the deployment.

Post deployment[edit]

  1. End-points are OK.
  2. Watch logstash: https://logstash.wikimedia.org/app/kibana?#/dashboard/cx-last-24-hours-error?_g=h@1f9dccc&_a=h@ba4bac6
  3. Test CX1 and CX2 again in Production.
  4. Watch: https://grafana.wikimedia.org/dashboard/db/service-cxserver

See also[edit]