tonyair/silverstripe-framework
1
0
Fork 0
mirror of https://github.com/silverstripe/silverstripe-framework synced 2024-10-22 14:05:37 +02:00
Code Issues Projects Releases Wiki Activity
5347d660a0
silverstripe-framework/.travis.yml

83 lines
4.2 KiB
YAML
Raw Normal View History

Test against php 7
2015-02-26 02:32:47 +01:00
language: php
Simplified travis builds (using external script)
2013-03-28 23:49:32 +01:00
Use container-based travis
2015-07-03 04:13:07 +02:00
sudo: false
Allow HHVM tests to run on new travis infrastructure
2015-07-18 23:16:27 +02:00
addons:
apt:
packages:
- tidy
Updated Travis-CI configuration to have a 4 build grid. The Travis config will now run tests on the following instances * 5.3 + SQLite * 5.3 + MySQL * 5.3 + PostgreSQL * 5.4 + MySQL In other words, with the exception of Windows tech (MSSQL + Win server) this is a wide-coverage build config.
2012-08-21 00:33:54 +02:00
env:
Running Travis+Behat through Selenium, save artifacts
2013-10-16 14:01:14 +02:00
global:
Added NPM tests Also simplified logic branching by introducing $PHPUNIT_TEST.
2016-05-02 22:59:51 +02:00
- TRAVIS_NODE_VERSION="4"
Re-enable travis artifacts on framework (#5807)
2016-07-14 04:53:21 +02:00
- ARTIFACTS_REGION=us-east-1
- ARTIFACTS_BUCKET=silverstripe-travis-artifacts
- secure: "jVR0iLTuvVfA6jKX5+A3AdUEs8Ps+r3SbL0zGR687K8IoSp3a/+JLH12zFCEexOuxwCtOhlMq8zoZsptCEduCDq+0payk5k6GjNVywFaWjJCV573JScdaHAtoumoHMUvua+Pxds0qKAD2XEYAcOR4Qu7S4HLJV6E1QqHg9PRW5s=" # Encrypted ARTIFACTS_KEY
- secure: "SDGv49c2Ee2YBz7dATE3WnHSVSvJiRJ2BVtRasVshdNDNz3NBRzh13C2fDwTGBU1J6PxiQaGTXBy/BGsvbYk2BvdzHVwozkBpHVSaCNdarpCJ5yZZTqKC3mpA1S5353r5tqronwFuMDpftzXnRMfLZGGQ4kYb9hjV55+FPUTFPk=" # Encrypted ARTIFACTS_SECRET
Updated Travis-CI configuration to have a 4 build grid. The Travis config will now run tests on the following instances * 5.3 + SQLite * 5.3 + MySQL * 5.3 + PostgreSQL * 5.4 + MySQL In other words, with the exception of Windows tech (MSSQL + Win server) this is a wide-coverage build config.
2012-08-21 00:33:54 +02:00
matrix:
Fast-finish Travis builds The PHP7 build includes code coverage, which makes it run a bit longer now. In general, we shouldn't wait for allowed_failures with build feedback. Travis seems to run builds (roughly) in order, so allowed_failures tend to prolong build times, since it only runs a few builds concurrently. We'll move the PHP7 build out of allowed_failures eventually, but I think the general concept still applies: There's little value in waiting around for allowed_failures builds. See https://blog.travis-ci.com/2013-11-27-fast-finishing-builds/
2016-09-26 22:19:41 +02:00
fast_finish: true
PHP 5.5 CI, don't allow failures for sqlite3 and postgres
2013-07-04 22:19:42 +02:00
include:
Increase minimum required PHP version to 5.5 See mailinglist discussion at https://groups.google.com/forum/#!topic/silverstripe-dev/7mVvhNNeNps
2015-10-22 11:10:19 +02:00
- php: 5.5
Added NPM tests Also simplified logic branching by introducing $PHPUNIT_TEST.
2016-05-02 22:59:51 +02:00
env: DB=PGSQL PHPUNIT_TEST=1
MINOR: Refine build matrix. It's important to test different databases. It's important to test different versions of PHP. But we don't need to test all possible versions of each tested in a cartesian product. This patch ensures that there are 4 builds that cover: - PHP 5.4, 5.5, 5.6 - MySQL, PostgreSQL and SQLite - PDO and each db-specific connector - Behat and non
2015-08-28 06:56:30 +02:00
- php: 5.6
NEW: Simplified test runs. We don’t use SQLite in production and so it doesn’t need to be part of our build matrix.
2016-10-26 05:16:35 +02:00
env: DB=MYSQL PHPUNIT_TEST=1
- php: 7.0
env: DB=MYSQL PDO=1 PHPUNIT_COVERAGE_TEST=1
Add PHP 5.6 to Travis
2014-03-13 08:47:52 +01:00
- php: 5.6
Added NPM tests Also simplified logic branching by introducing $PHPUNIT_TEST.
2016-05-02 22:59:51 +02:00
env: DB=MYSQL BEHAT_TEST=1
NEW: Move Travis behat test to run locally. This shifts the behat test run to be triggered form composer activity within the framework module directly, * silverstripe/serve is used to provide a webserver, based on the php -S command * se/selenium-server-standalone is used to install selenium rather than a download command Because we’re using serve, the behat configuration can be locked down. Further refinements could be made on this: * the behat-extension could be responsible for installing and starting/stopping selenium, making these tests more portable * xvfb initialisation could be provided with another bin tool in the begat-extension: vendor/bin/xvfb 1024x768 * The bootstrap-file argument to serve could be provided as part of a composer.json setting. This would make it easier for developers to start a dev server simply by running vendor/bin/serve * the behat-extension could be responsible for installing and starting/stopping silverstripe/serve, removing the need for specifying base_url at all, and possibly utilising the same bootstrap file between serve and behat.
2016-09-13 08:23:31 +02:00
- php: 5.6
env: NPM_TEST=1
Restore CMS build to CI
2016-09-21 22:31:56 +02:00
- php: 5.6
env: DB=MYSQL CMS_TEST=1 PHPUNIT_TEST=1
- php: 5.6
env: DB=MYSQL CMS_TEST=1 BEHAT_TEST=1
NEW: Move Travis behat test to run locally. This shifts the behat test run to be triggered form composer activity within the framework module directly, * silverstripe/serve is used to provide a webserver, based on the php -S command * se/selenium-server-standalone is used to install selenium rather than a download command Because we’re using serve, the behat configuration can be locked down. Further refinements could be made on this: * the behat-extension could be responsible for installing and starting/stopping selenium, making these tests more portable * xvfb initialisation could be provided with another bin tool in the begat-extension: vendor/bin/xvfb 1024x768 * The bootstrap-file argument to serve could be provided as part of a composer.json setting. This would make it easier for developers to start a dev server simply by running vendor/bin/serve * the behat-extension could be responsible for installing and starting/stopping silverstripe/serve, removing the need for specifying base_url at all, and possibly utilising the same bootstrap file between serve and behat.
2016-09-13 08:23:31 +02:00
allow_failures:
Include CMS smoke tests in Travis builds We've had a few failures where framework caused regressions in CMS, so these builds are helpful. They'll increase the overall build times on the "silverstripe" user because of Travis' build limitations. The parallel per-build run times shouldn't increase, since framework builds take longer than cms builds anyway: CMS Behat build took 13:53 on last 3.3 run, framework MySQL PDO build took 16:12.
2016-03-06 23:50:51 +01:00
- php: 5.6
Added NPM tests Also simplified logic branching by introducing $PHPUNIT_TEST.
2016-05-02 22:59:51 +02:00
env: DB=MYSQL CMS_TEST=1 PHPUNIT_TEST=1
Include CMS smoke tests in Travis builds We've had a few failures where framework caused regressions in CMS, so these builds are helpful. They'll increase the overall build times on the "silverstripe" user because of Travis' build limitations. The parallel per-build run times shouldn't increase, since framework builds take longer than cms builds anyway: CMS Behat build took 13:53 on last 3.3 run, framework MySQL PDO build took 16:12.
2016-03-06 23:50:51 +01:00
- php: 5.6
Added NPM tests Also simplified logic branching by introducing $PHPUNIT_TEST.
2016-05-02 22:59:51 +02:00
env: DB=MYSQL CMS_TEST=1 BEHAT_TEST=1
Added support for Travis CI
2012-08-14 06:02:12 +02:00
before_script:
Merge 3 into master # Conflicts: # .travis.yml # admin/css/ie7.css # admin/css/ie7.css.map # admin/css/ie8.css.map # admin/css/screen.css # admin/css/screen.css.map # admin/javascript/LeftAndMain.js # admin/scss/_style.scss # admin/scss/_uitheme.scss # control/HTTPRequest.php # core/Object.php # css/AssetUploadField.css # css/AssetUploadField.css.map # css/ConfirmedPasswordField.css.map # css/Form.css.map # css/GridField.css.map # css/TreeDropdownField.css.map # css/UploadField.css # css/UploadField.css.map # css/debug.css.map # dev/Debug.php # docs/en/00_Getting_Started/00_Server_Requirements.md # docs/en/02_Developer_Guides/06_Testing/00_Unit_Testing.md # docs/en/02_Developer_Guides/06_Testing/index.md # docs/en/02_Developer_Guides/14_Files/02_Images.md # docs/en/02_Developer_Guides/15_Customising_the_Admin_Interface/How_Tos/Extend_CMS_Interface.md # filesystem/File.php # filesystem/Folder.php # filesystem/GD.php # filesystem/Upload.php # forms/ToggleField.php # forms/Validator.php # javascript/lang/en_GB.js # javascript/lang/fr.js # javascript/lang/src/en.js # javascript/lang/src/fr.js # model/Image.php # model/UnsavedRelationList.php # model/Versioned.php # model/connect/MySQLDatabase.php # model/fieldtypes/DBField.php # model/fieldtypes/Enum.php # scss/AssetUploadField.scss # scss/UploadField.scss # templates/email/ChangePasswordEmail.ss # templates/forms/DropdownField.ss # tests/behat/features/bootstrap/SilverStripe/Framework/Test/Behaviour/CmsFormsContext.php # tests/behat/features/bootstrap/SilverStripe/Framework/Test/Behaviour/CmsUiContext.php # tests/forms/EnumFieldTest.php # tests/security/MemberTest.php # tests/security/MemberTest.yml # tests/security/SecurityTest.php
2016-04-29 07:50:55 +02:00
- printf "\n" | pecl install imagick
Make travis more resilient to composer self-update `composer self-update` has been failing regularly on travis recently. As `composer` is already installed and it's not strictly essential to have the very latest version, this change allows the build to continue, even if composer can't self-update
2015-06-12 20:41:24 +02:00
- composer self-update || true
NEW Amend Travis build to run a simple PHP_CodeSniffer test. At this stage, the test just checks line-length and line-endings, but previous commits have ensured that framework actually passes those tests. We can add more tests as we actually correct the code to pass those tests, and grow the test suite, as we had for unit tests.
2012-09-26 23:35:17 +02:00
- phpenv rehash
Disable xdebug on Travis runs We're not using it for code coverage, and it's slowing down both composer and phpunit builds. Recommended by Travis: https://docs.travis-ci.com/user/speeding-up-the-build/#PHP-optimisations
2016-03-07 02:05:53 +01:00
- phpenv config-rm xdebug.ini
NEW: Move Travis behat test to run locally. This shifts the behat test run to be triggered form composer activity within the framework module directly, * silverstripe/serve is used to provide a webserver, based on the php -S command * se/selenium-server-standalone is used to install selenium rather than a download command Because we’re using serve, the behat configuration can be locked down. Further refinements could be made on this: * the behat-extension could be responsible for installing and starting/stopping selenium, making these tests more portable * xvfb initialisation could be provided with another bin tool in the begat-extension: vendor/bin/xvfb 1024x768 * The bootstrap-file argument to serve could be provided as part of a composer.json setting. This would make it easier for developers to start a dev server simply by running vendor/bin/serve * the behat-extension could be responsible for installing and starting/stopping silverstripe/serve, removing the need for specifying base_url at all, and possibly utilising the same bootstrap file between serve and behat.
2016-09-13 08:23:31 +02:00
- "export DISPLAY=\":99\""
- "export XVFBARGS=\":99 -ac -screen 0 1024x768x16\""
FIX: Make PR builds work. PR builds are consistently failing because the version of framework being used cannot be inferred. This environment variable provides the answer. It will need to be fixed for each major release, but I think that’s less maintenance burden than complicating the build script to read this from composer.json:extra.branch-alias.dev-master.
2016-09-20 23:26:29 +02:00
- "export COMPOSER_ROOT_VERSION=4.0.x-dev"
NEW: Move Travis behat test to run locally. This shifts the behat test run to be triggered form composer activity within the framework module directly, * silverstripe/serve is used to provide a webserver, based on the php -S command * se/selenium-server-standalone is used to install selenium rather than a download command Because we’re using serve, the behat configuration can be locked down. Further refinements could be made on this: * the behat-extension could be responsible for installing and starting/stopping selenium, making these tests more portable * xvfb initialisation could be provided with another bin tool in the begat-extension: vendor/bin/xvfb 1024x768 * The bootstrap-file argument to serve could be provided as part of a composer.json setting. This would make it easier for developers to start a dev server simply by running vendor/bin/serve * the behat-extension could be responsible for installing and starting/stopping silverstripe/serve, removing the need for specifying base_url at all, and possibly utilising the same bootstrap file between serve and behat.
2016-09-13 08:23:31 +02:00
- "if [ \"$na\" = \"\" ]; then composer install --prefer-dist; fi"
- "if [ \"$DB\" = \"PGSQL\" ]; then composer require silverstripe/postgresql:2.0.x-dev --prefer-dist; fi"
- "if [ \"$DB\" = \"SQLITE\" ]; then composer require silverstripe/sqlite3:2.0.x-dev --prefer-dist; fi"
- "if [ \"$CMS_TEST\" = \"1\" ]; then COMPOSER_ROOT_VERSION=4.0.x-dev composer require silverstripe/cms:4.0.x-dev silverstripe/siteconfig:4.0.x-dev silverstripe/reports:4.0.x-dev --prefer-dist; fi"
NEW: Ignore npm-shrinkwrap for greenskeeper-provided PRs.
2016-09-17 05:31:12 +02:00
- "if [ \"$NPM_TEST\" = \"1\" ] && [ `git log --format=format:%aE -1` = \"support@greenkeeper.io\" ]; then echo \"Removing npm-shrinkwrap.json\"; rm npm-shrinkwrap.json; fi"
NEW: Use sass-lint over scss-lint SCSS linting now uses the node-based sass-lint tool, since we’re shifting away from CodeClimate. This has the benefit of not requiring a ruby gem on dev tools - everything is provided as npm dev dependencies. This was also necessary to run the linting inside travis.
2016-09-17 05:30:30 +02:00
- "if [ \"$NPM_TEST\" = \"1\" ]; then nvm install $TRAVIS_NODE_VERSION && npm install; fi"
NEW: Move Travis behat test to run locally. This shifts the behat test run to be triggered form composer activity within the framework module directly, * silverstripe/serve is used to provide a webserver, based on the php -S command * se/selenium-server-standalone is used to install selenium rather than a download command Because we’re using serve, the behat configuration can be locked down. Further refinements could be made on this: * the behat-extension could be responsible for installing and starting/stopping selenium, making these tests more portable * xvfb initialisation could be provided with another bin tool in the begat-extension: vendor/bin/xvfb 1024x768 * The bootstrap-file argument to serve could be provided as part of a composer.json setting. This would make it easier for developers to start a dev server simply by running vendor/bin/serve * the behat-extension could be responsible for installing and starting/stopping silverstripe/serve, removing the need for specifying base_url at all, and possibly utilising the same bootstrap file between serve and behat.
2016-09-13 08:23:31 +02:00
- "if [ \"$BEHAT_TEST\" = \"1\" ]; then sh -e /etc/init.d/xvfb start; sleep 3; fi"
- "if [ \"$BEHAT_TEST\" = \"1\" ]; then (vendor/bin/selenium-server-standalone > selenium.log 2>&1 &); fi"
- "if [ \"$BEHAT_TEST\" = \"1\" ]; then (vendor/bin/serve --bootstrap-file tests/behat/serve-bootstrap.php &> serve.log &); fi"
Test against php 7
2015-02-26 02:32:47 +01:00
script:
NEW: Don’t set up SilverStripe project for test run The SilverStripe project structure complicates the travis test run, and the goal of this branch is to prevent it from being necessary. - Unit tests can be run simply with PHPUnit. - Behat test can be run with the silverstripe/serve module Note that initially this commit doesn’t cater to the behat tests. As part of this, we allow dev packages to be installed when testing These settings don’t affect projects that use framework, only when framework’s composer install / require calls are used themselves. Since SS4 is pre-stable, these are important. They can probably be removed once SS4 stable (and stable versions of support packages) have been released.
2016-09-12 07:42:05 +02:00
- "if [ \"$PHPUNIT_TEST\" = \"1\" ] && [ \"$CMS_TEST\" = \"\" ]; then vendor/bin/phpunit; fi"
Added NPM tests Also simplified logic branching by introducing $PHPUNIT_TEST.
2016-05-02 22:59:51 +02:00
- "if [ \"$PHPUNIT_TEST\" = \"1\" ] && [ \"$CMS_TEST\" = \"1\" ]; then vendor/bin/phpunit cms/tests; fi"
NEW: Move Travis behat test to run locally. This shifts the behat test run to be triggered form composer activity within the framework module directly, * silverstripe/serve is used to provide a webserver, based on the php -S command * se/selenium-server-standalone is used to install selenium rather than a download command Because we’re using serve, the behat configuration can be locked down. Further refinements could be made on this: * the behat-extension could be responsible for installing and starting/stopping selenium, making these tests more portable * xvfb initialisation could be provided with another bin tool in the begat-extension: vendor/bin/xvfb 1024x768 * The bootstrap-file argument to serve could be provided as part of a composer.json setting. This would make it easier for developers to start a dev server simply by running vendor/bin/serve * the behat-extension could be responsible for installing and starting/stopping silverstripe/serve, removing the need for specifying base_url at all, and possibly utilising the same bootstrap file between serve and behat.
2016-09-13 08:23:31 +02:00
- "if [ \"$BEHAT_TEST\" = \"1\" ] && [ \"$CMS_TEST\" = \"\" ]; then vendor/bin/behat --config tests/behat/config.yml .; fi"
- "if [ \"$BEHAT_TEST\" = \"1\" ] && [ \"$CMS_TEST\" = \"1\" ]; then vendor/bin/behat @cms --config cms/tests/behat/behat.yml; fi"
Added NPM tests Also simplified logic branching by introducing $PHPUNIT_TEST.
2016-05-02 22:59:51 +02:00
- "if [ \"$NPM_TEST\" = \"1\" ]; then npm run test; fi"
NEW: Run JS/CSS linting in Travis. The ‘npm run lint’ command will be used to run listing on Travis, which can also be used on local dev environments. These can also be used with editor plugins to highlight errors immediately. The intention is that this can be used in place of codeclimate. The benefits are that we use a single toolchain in both CI and local dev, which is not entirely the case at the moment. Note the sass-lint is provided by “sudo gem install scss_lint”. It’s possible that we can move to a node-based sass-lint; I can’t recall what the motivation for using the scss_lint gem was - I think it was mainly that we had the AirBNB styleguide already implemented as a linter config.
2016-09-15 08:12:55 +02:00
- "if [ \"$NPM_TEST\" = \"1\" ]; then npm run lint; fi"
Code coverage via CodeCov on PHP7 builds PHP7+phpdbg is waaaay faster: http://blog.remirepo.net/post/2015/11/09/PHPUnit-code-coverage-benchmark
2016-09-26 04:39:28 +02:00
- "if [ \"$PHPUNIT_COVERAGE_TEST\" = \"1\" ] && [ \"$CMS_TEST\" = \"\" ]; then phpdbg -qrr ./vendor/bin/phpunit --coverage-clover=coverage.xml; fi"
- "if [ \"$PHPUNIT_COVERAGE_TEST\" = \"1\" ] && [ \"$CMS_TEST\" = \"\" ]; then bash <(curl -s https://codecov.io/bash) -f coverage.xml; fi"
Proof-of-concept of running Firefox Behat in Travis-CI
2013-10-02 05:04:31 +02:00
after_failure:
Re-enable travis artifacts on framework (#5807)
2016-07-14 04:53:21 +02:00
- php ~/travis-support/travis_upload_artifacts.php --if-env BEHAT_TEST,ARTIFACTS_BUCKET,ARTIFACTS_KEY,ARTIFACTS_SECRET --target-path $TRAVIS_REPO_SLUG/$TRAVIS_BUILD_ID/$TRAVIS_JOB_ID --artifacts-base-url https://s3.amazonaws.com/$ARTIFACTS_BUCKET/
Added IRC notifications to Travis
2012-09-03 03:20:11 +02:00
Travis branch exclusions
2012-10-16 10:25:18 +02:00
branches:
except:
- 2.1
- 2.2
- 2.3
- translation-staging
Proof-of-concept of running Firefox Behat in Travis-CI
2013-10-02 05:04:31 +02:00
# global:
# - secure: "AZmjVPtUD8JBA7ag4ULlEwEKXSEZbIUjDHeRBFugaOtdsn5yigGLmwYbzsg2tq7k7UkdbbAlGct0SUbiRJb9F2wPA5+eUd/p49fgDIU6CTSWIlT87H2BwgOrxKwS9sDwxLptPFM6vWQ8JKYSNGmVIepie9kQZbu4L2k5k6B69jQ="
# - secure: "f3kKpUn9cS5K+p/E52cMqN18cDApol/43LanDmHO6mo3iRAztk3jZLyfNOUq6JASKMqdh8+9kencRpEoaAYbcQnDPoZsT9POResiJ9/ADKB6RwWy+lcFHUp9E2Zf/x2VRh9FmXEguDhpWzkJqzWYJGCSig1IBp/+TjzKnsjQHIY="
#
# - php ~/travis-support/travis_setup_sauceconnect.php --if-env BEHAT_TEST --username ${SAUCE_USERNAME} --access-key ${SAUCE_ACCESS_KEY} --tunnel-identifier ${TRAVIS_JOB_NUMBER} --base-url http://localhost
Reference in New Issue Copy Permalink