Continuous integration

Wikimedia engineering activity

Continuous integration

A testing platform to provide continuous quality control for MediaWiki

Group:	Platform
Start:
End:
Team:	Timo Tijhof, Chad Horohoe
Lead:	Antoine Musso
Status:	See updates

← Legacy server

The continuous integration infrastructure uses Jenkins (run from gallium) to control and execute builds.

Related services are reachable from its dashboard:

integration.wikimedia.org

Learn how to add new checks in the tutorials.

Status

• [edit status] • [add new]
  2014-03-monthly:
  Erik Bernhardson and Chad Horohoe created jobs using Jenkins Job Builder (JJB) based on the tutorials on installing JJB and Adding a MediaWiki extension.

System health

• Integration - Nagf Monitoring for Continuous integration slaves.

Rationale

In order to improve the development process, it was proposed to consolidate a platform to run automated tests systematically at pre-commit or post-commit time.

These tests aim to check that the master branch of our repositories in git remain in an (almost) constantly deployable state. This project also relates to the will to have more frequent code deployments, as continuous integration will give us more confidence in new code if it already passed the automated tests.

Documents

Architecture/Isolation	Browser tests	Dev
Documentation generation	Git repositories	Jenkins
Jenkins job builder	Legacy server	Overhaul
PHP CodeSniffer	Parsoid	Test entry points
Tutorials	Tutorials/Adding a MediaWiki extension	Tutorials/Adding basic checks
Tutorials/Test your python	Tutorials/Trigger a job manually	Virtual Machine
Workflow	Workflow v1 specification	Workflow v2 specification
Zuul	Zuul/gearman upgrade	grunt
status

See also

• Continuous integration project in Phabricator (Workboard for open issues)
• integration user group in Gerrit
• Manual:Unit testing
• the Beta cluster is constantly updated with the latest code from git master for MediaWiki core and many extensions.