Hello, Earlier today I have slightly changed our review / test workflow on mediawiki/core.git . That will let us do more tests and scale things in the long term. The new workflow is described on the wiki (including a flowchart): https://www.mediawiki.org/wiki/Continuous_integration/Workflow How it works? Whenever a patch is submitted, Jenkins will attempt to merge the patchset against the latest master and abort whenever it fails asking for the submitter to rebase the patchset. Jenkins will then verify the PHP files are valid and run JSHint for the Javascript files. If everything is fine, jenkins-bot will vote Code-Review +1 to let everyone know that the change look fine. Else, it will vote Verified -1 preventing the patchset from being submitted. That is all. The slow unit tests are no more run on patchset submission. To get the test to run, the patch will have to be reviewed first. Whenever someone vote CodeReview +2 Jenkins will run the Unit tests, then if: - tests are successful, jenkins-bot will vote Verified+1 which let us merge the patch. - tests are failing, jenkins-bot vote Verified-1 AND CodeReview -2 to prevent the patch from being merged. If all works fine tonight, I will configure jenkins-bot so it merges the Change automatically whenever the test are successful. That workflow has been applied to a few extensions this week. I will add it to more and more extensions and eventually will get all extensions to receive PHP Linting and a JSHint run. -- Antoine "hashar" Musso