Remove configuration for Travis CI

[bbatsche]

Testing triggered builds on Jenkins

[BaDos]

Unit & Integration Test Results

✅ All unit and integration tests have passed.

Unit Test Output

> phpunit --configuration tests/unit '--log-junit' 'tests/unit/tmp/junit.xml' '--coverage-clover' 'tests/unit/tmp/clover.xml'
PHPUnit 7.5.20 by Sebastian Bergmann and contributors.

.............................................................   61 / 1454 (  4%)
.............................................................  122 / 1454 (  8%)
.............................................................  183 / 1454 ( 12%)
.............................................................  244 / 1454 ( 16%)
.............................................................  305 / 1454 ( 20%)
.............................................................  366 / 1454 ( 25%)
.............................................................  427 / 1454 ( 29%)
.............................................................  488 / 1454 ( 33%)
.............................................................  549 / 1454 ( 37%)
.............................................................  610 / 1454 ( 41%)
.............................................................  671 / 1454 ( 46%)
.............................................................  732 / 1454 ( 50%)
.............................................................  793 / 1454 ( 54%)
.............................................................  854 / 1454 ( 58%)
.............................................................  915 / 1454 ( 62%)
.............................................................  976 / 1454 ( 67%)
............................................................. 1037 / 1454 ( 71%)
............................................................. 1098 / 1454 ( 75%)
............................................................. 1159 / 1454 ( 79%)
............................................................. 1220 / 1454 ( 83%)
............................................................. 1281 / 1454 ( 88%)
............................................................. 1342 / 1454 ( 92%)
............................................................. 1403 / 1454 ( 96%)
...................................................           1454 / 1454 (100%)

Time: 30.94 seconds, Memory: 78.00 MB

OK (1454 tests, 4586 assertions)

Generating code coverage report in Clover XML format ... done

Integration Test Output

> phpunit --configuration tests/integration '--log-junit' 'tests/integration/tmp/junit.xml'
PHPUnit 7.5.20 by Sebastian Bergmann and contributors.

................................................................. 65 / 65 (100%)


Time: 6.58 seconds, Memory: 28.00 MB

OK (65 tests, 69 assertions)

This comment was generated by Jenkins job ece-tools/unit build 70.

[BaDos]

Static Analysis & Code Style Results

✅ All static analysis and code style checks have passed.

PHP Codesniffer Output

> phpcs src --standard=tests/static/phpcs-ruleset.xml -p -n
............................................................  60 / 689 (9%)
............................................................ 120 / 689 (17%)
............................................................ 180 / 689 (26%)
............................................................ 240 / 689 (35%)
............................................................ 300 / 689 (44%)
............................................................ 360 / 689 (52%)
............................................................ 420 / 689 (61%)
............................................................ 480 / 689 (70%)
............................................................ 540 / 689 (78%)
............................................................ 600 / 689 (87%)
............................................................ 660 / 689 (96%)
.............................                                689 / 689 (100%)


Time: 36.6 secs; Memory: 24MB

PHP Mess Detector Output

Found 0 violations and 0 errors in 20756ms

�[32mNo mess detected�[0m

PHPStan Output

> phpstan analyse -c tests/static/phpstan.neon '--no-progress'

������  You're running a really old version of PHPStan.���

The last release in the 0.11.x series with new features
and bugfixes was released on October 22nd 2019,
that's 415 days ago.

Since then more than 50 new PHPStan versions were released
with hundreds of new features, bugfixes, and other
quality of life improvements.

To learn about what you're missing out on, check out
this blog with articles about the latest major releases:
https://phpstan.org/blog

Historically, the main two blockers preventing
people from upgrading were:
1) Composer conflicts with other dependencies.
2) Errors discovered by the new PHPStan version and no time
   to fix them to get to a green build again.

Today, neither of them is a problem anymore thanks to:
1) phpstan/phpstan package having zero external dependencies.
2) Baseline feature letting you use the latest release
   right away even with pre-existing errors.
   Read more about it here: https://phpstan.org/user-guide/baseline

Upgrade today to PHPStan 0.12 by using
"phpstan/phpstan": "^0.12" in your composer.json.


������  You're running a really old version of PHPStan.���

The last release in the 0.11.x series with new features
and bugfixes was released on October 22nd 2019,
that's 415 days ago.

Since then more than 50 new PHPStan versions were released
with hundreds of new features, bugfixes, and other
quality of life improvements.

To learn about what you're missing out on, check out
this blog with articles about the latest major releases:
https://phpstan.org/blog

Historically, the main two blockers preventing
people from upgrading were:
1) Composer conflicts with other dependencies.
2) Errors discovered by the new PHPStan version and no time
   to fix them to get to a green build again.

Today, neither of them is a problem anymore thanks to:
1) phpstan/phpstan package having zero external dependencies.
2) Baseline feature letting you use the latest release
   right away even with pre-existing errors.
   Read more about it here: https://phpstan.org/user-guide/baseline

Upgrade today to PHPStan 0.12 by using
"phpstan/phpstan": "^0.12" in your composer.json.


 [OK] No errors                                                                 

This comment was generated by Jenkins job ece-tools/static build 66.

[BaDos]

Functional Acceptance Test Results

✅ All functional acceptance tests have passed.

PHP 7.1

• ✅ ElasticSearch22Cest
• ✅ AcceptanceCe71Cest
• ✅ Cron21Cest
• ✅ Upgrade21Cest
• ✅ Upgrade22Cest
• ✅ RedisPhp71Cest
• ✅ AdminCredential21Cest
• ✅ AdminCredential22Cest
• ✅ Cron22Cest

PHP 7.2

• ✅ ElasticSearch23Php72Cest
• ✅ AcceptanceCe72Cest
• ✅ Cron23Php72Cest
• ✅ Upgrade23Cest
• ✅ AdminCredential23Php72Cest
• ✅ RedisPhp72Cest
• ✅ RedisPhp72GoodConfigCest

PHP 7.3

• ✅ ElasticSearch23Php73Cest
• ✅ AcceptanceCe73Cest
• ✅ BackupDb23Cest
• ✅ SplitDb73Cest
• ✅ UpgradeCest
• ✅ ErrorCodes23Cest
• ✅ SplitDbWizard73Cest
• ✅ Cron23Php73Cest
• ✅ AdminCredential23Cest
• ✅ RedisPhp73Cest

PHP 7.4

• ✅ AcceptanceCeCest
• ✅ ElasticSearchCest
• ✅ BackupDbCest
• ✅ CronCest
• ✅ DataTypesOptionValidationCest
• ✅ ErrorMessageCest
• ✅ CronUnlockCest
• ✅ ScenarioExtensibilityCest
• ✅ SplitDbWizardCest
• ✅ ErrorCodesCest
• ✅ SessionConfigurationCest
• ✅ AdminCredentialCest
• ✅ PostDeployCest
• ✅ DatabaseConfigurationCest
• ✅ ScdStrategyCest
• ✅ ScdMatrixCest
• ✅ SplitDbCest
• ✅ WizardScdCest
• ✅ RedisCest
• ✅ ReportDirNestingLevelCest
• ✅ AcceptanceCest

Output for failed tests is below. If more than 5 tests have failed only the first 5 will be included. If you need additional information please reach out to the Magento Cloud team for more details.

This comment was generated by Jenkins job ece-tools/functional build 301.