Last modified: 2014-07-14 23:13:26 UTC
For consideration. Though concurrency is nice, separate jobs also comes at a set up cost: * wipe workspace * git-fetch * git-checkout * install mediawiki * init phpunit * occupying one of 10 jenkins executors etc. Since phpunit tests already are running in the same build (each phpunit-group contains various different subgroups and test suites). The separation we use now is mostly arbitrary from the tests point of view, it should be fine to run them in the same build. I think it would be faster to run them concurrently within one job. Also keeps the statistics and jUnit report card more complete by not being spread over three build histories.
https://github.com/verkkokauppacom/parallel-phpunit
Gist from Sebastian Bergmann, PHPUnit creator: partition-testsuite.php Script that (making way too many assumptions) generates an Apache Ant build script to run a PHPUnit test suite in parallel. https://gist.github.com/sebastianbergmann/4405417 Then assemble the generated JUnit XML files using: merge-phpunit-xml.php Script that merges multiple PHPUnit XML logfiles (JUnit XML) into one PHPUnit XML logfile. https://gist.github.com/sebastianbergmann/4405658
