See this article for details:
https://scrutinizer-ci.com/docs/tools/php/php-analyzer/guides/migrate_to_new_php_analysis



Signed-off-by: Stefan Weil <sw@weilnetz.de>

Signed-off-by: Lukas Reschke <lukas@statuscode.ch>

Scrutinizer otherwise complains about the fact that some classes are undefined etc.

Let's see whether that works 

Let's see if this helps for cases such as https://github.com/owncloud/core/issues/19793

Our test execution is terribly slow and now also exceeds more than one hour on our CI system. This means that Scrutinizer fails hard on a lot of PRs such as https://github.com/owncloud/core/pull/17217#issuecomment-116252420

Hopefully fixes problems with unfinished scrutinizer reports

* use PHPUnit 4.x
* force php memory limit on travis to 1024MB
* create script for travis
* whitelist branches master, stable5 and stable6 on travis (and PRs)
* sqlplus64
* conditional JS tests and ocular temporal removal
* enable scrutinizer code coverage
* move oracle to top to decrease overall test duration