Some tests compare the result to english strings.
Do not test UnixCommandExecutor on Windows.
PharTest: explain why PHAR writing test are skipped.
InstallCommandTest: mock checkRequirements to allow the tests to run.
Run php_parallel_lint before all other tests.
Close#846
This variable allows to change where the build happens.
It defaults to PHPCI_DIR.'PHPCI/build/'.
Moved build path calculate and build removal into the Build class.
Also remove the build directory when deleting the build.
Close#834
Fixed docblocks.
Reworked WebhookController to enforce Json responses in ::handleAction.
Check the project type match the webhook.
When creating several builds, do not stop on first error.
Try to create every builds and report 'ok' if at least one succeeds.
CS fix.
Fixed Uses.
Fixed the types accepted by the git webhook.
Added some really basic test.
Added another test case from #571.
Updated the output of TapParser::processTestLine.
Broke TapParser::parse down in simpler methods.
TapParser: ignore leading garbage and properly complain on missing TAP log.
TapParser: detect and report duplicated TAP log.
TapParser: got rid of the "test" and "suite" values.
They are only available with PHPUnit.
TapParser: append the message from yaml diagnostic to existing message.
Reworked the dispaly of test results.
PHPUnit plugin: pretty print test data.
Added an AnsiConverter helper.
Use the AnsiConverter in the email and page templates that display the build log.
Use a dedicated stylesheet for the ANSI converter.
It can be customized.
It can be inlined in the notifications.
Do not use ProphecyTestCase when not needed.
This occurs commonly on Windows, but from my reading of the code it would also be a problem on other platforms if spaces were present (though this is less likely, due to different naming conventions).
It has been fixed by using escapeshellarg() on both of the paths used in the command.
Fixes#698, which I've just noticed has a similar solution suggested in one of the comments, but was closed without anyone actually implementing it.
All the DB/host fields have a space after the colon, which is much better as it means the text you type is slightly separated from the prompt. However, the admin user fields didn't include this space which was inconsistent and made the install script a little less professional.
I have therefore added the missing space for the prompts which didn't have it in the English language file, and have also updated all other language files to also use this format. Most of them followed the same inconsistency as the English version, though some were consistent but without a space, and some which were differently inconsistent (both internally, and between languages).
