Hello,

I have crafted and enabled two new jobs:

* mediawiki-phpunit-hhvm * mediawiki-phpunit-zend

Which are triggered whenever a patch is proposed to the repos:

mediawiki/core mediawiki/vendor

Or the mobile related extensions:

Echo JsonConfig Mantle MobileApp MobileFrontend VisualEditor WikiGrok ZeroBanner ZeroPortal

The jobs clone all of those repositories and run the MediaWiki core extension test suite, ie:

cd tests/phpunit php phpunit.php --testsuite extensions

They are NOT run on old branches (REL1_19, REL1_22, REL1_23, REL1_24), the old jobs are.

They are run (and pass) on master and wmf branches and will on future REL branch (ie REL1_25).

They do NOT run the MediaWiki core main tests suites cause that is awfully slow. The previous jobs weren't either.

On mediawiki/core and mediawiki/vendor we still run the core tests though (mediawiki-phpunit-{hhvm,zend}).

_ / \ / | \ /__.__\

Side effect: if one deprecates a function/method in mediawiki/core and it is used by one of the extensions above, the job will fail until the extensions above have been adjusted.

I hope to add more extensions to that list. Additionally I am looking to add a command to verify whether an extension is a good candidate for inclusion.

For more context/details see:

[WikimediaMobile] Testing extensions together https://lists.wikimedia.org/pipermail/mobile-l/2014-December/008398.html

Gerrit change https://gerrit.wikimedia.org/r/#/c/180494/

RFC Task https://phabricator.wikimedia.org/T1350

The RFC itself: https://www.mediawiki.org/wiki/Requests_for_comment/Extensions_continuous_in...