Continuous integration

Wikimedia Foundation project Continuous integration A testing platform to provide continuous quality control for MediaWiki Group: Release Engineering Start: June 2011 Team members: Dan Duvall, Tyler Cipriani, Timo Tijhof Lead: Antoine Musso ← Legacy server

The continuous integration infrastructure uses Jenkins to control and execute builds. The main use is to run tests on patches submitted on Gerrit.

Related services are reachable from its dashboard at integration.wikimedia.org.

Documentation

• Entry points: Standardised tests for projects.
• Tutorials: Learn how to create and enable Jenkins jobs.

Coordination

• #wikimedia-releng ^connect and #wikimedia-dev ^connect
• Monitoring for Jenkins slaves (Nagf)
• Infrastructure Workboard (Phabricator)
• Git "integration" user group (Gerrit)

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

• Allow list
• Architecture/Castor
• Architecture/Isolation
• Architecture/Troubleshooting
• Browser tests
• Codehealth Pipeline
• Dev
• Docker
• Docker/Dockerfiles
• Documentation generation
• Entry points
• Git repositories
• Jenkins
• Jenkins job builder
• Legacy server
• Meetings
• Overhaul
• Ownership of Selenium Jenkins job
• PHP CodeSniffer
• Parsoid
• Phan
• Phan/Phan-taint-check-plugin
• Phan/Phan-taint-check-plugin/Security issues found
• Qemu
• Quibble
• SonarQube Scanner
• Tutorials
• Tutorials/Add phan to a MediaWiki extension
• Tutorials/Adding a MediaWiki extension
• Tutorials/Adding a new release pipeline for MediaWiki
• Tutorials/Adding basic checks
• Tutorials/Adding your extension to the shared gate job
• Tutorials/Debian packaging
• Tutorials/Generating PHP test coverage for a MediaWiki extension
• Tutorials/Test your Python
• Tutorials/Testing your go
• Tutorials/Trigger a job manually
• Understanding build failures
• Virtual Machine
• Workflow
• Workflow 2013
• Workflow 2014
• Zuul
• Zuul/gearman upgrade
• status

See also

• Nodepool
• Manual:Unit testing with MediaWiki
• Beta cluster: Automatically updated to latest master of MediaWiki core and extensions when commits are merged.