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
f769d9a13f
silverstripe-framework/.travis.yml

59 lines
2.5 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
matrix:
PHP 5.5 CI, don't allow failures for sqlite3 and postgres
2013-07-04 22:19:42 +02:00
include:
MINOR: Simplify build matrix for 3.x builds. This is a companion to https://github.com/silverstripe/silverstripe-framework/pull/4556 but targeted at the build needs of SilverStripe 3.x. Commit into 3.1 and then the merge forward into 3.2 and 3.
2015-08-29 05:50:49 +02:00
- php: 5.3
Reformat .travis.yml
2014-08-22 00:24:32 +02:00
env: DB=MYSQL
BUG Fix PDOConnector issues Travis support for PDO ATTR_EMULATE_PREPARES = false breaks some test cases Enable username sans password Remove unnecessary semicolons delimiting queries
2014-08-01 07:56:21 +02:00
- php: 5.4
MINOR: Simplify build matrix for 3.x builds. This is a companion to https://github.com/silverstripe/silverstripe-framework/pull/4556 but targeted at the build needs of SilverStripe 3.x. Commit into 3.1 and then the merge forward into 3.2 and 3.
2015-08-29 05:50:49 +02:00
env: DB=PGSQL
PHP 5.5 CI, don't allow failures for sqlite3 and postgres
2013-07-04 22:19:42 +02:00
- php: 5.5
MINOR: Simplify build matrix for 3.x builds. This is a companion to https://github.com/silverstripe/silverstripe-framework/pull/4556 but targeted at the build needs of SilverStripe 3.x. Commit into 3.1 and then the merge forward into 3.2 and 3.
2015-08-29 05:50:49 +02:00
env: DB=SQLITE
- php: 5.6
env: DB=MYSQL PDO=1
Add PHP 5.6 to Travis
2014-03-13 08:47:52 +01:00
- php: 5.6
Reformat .travis.yml
2014-08-22 00:24:32 +02:00
env: DB=MYSQL BEHAT_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
env: DB=MYSQL CMS_TEST=1
- php: 5.6
env: DB=MYSQL BEHAT_TEST=1 CMS_TEST=1
Added support for Travis CI
2012-08-14 06:02:12 +02:00
before_script:
FIX: Ensure that builds use the 3.4 dependencies. This fix does it in a way that doesn’t need manual maintenance per-branch
2016-11-03 02:47:30 +01:00
- export CORE_RELEASE=$TRAVIS_BRANCH
BUG Don't install imagick on php 5.3
2016-03-07 22:24:50 +01:00
- if ! [ $(phpenv version-name) = "5.3" ]; then printf "\n" | pecl install imagick; fi
trying to fix imagik properly
2016-03-08 16:05:16 +01:00
- if [ $(phpenv version-name) = "5.3" ]; then printf "\n" | pecl install imagick-3.3.0; fi
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
Simplified travis builds (using external script)
2013-03-28 23:49:32 +01:00
- git clone git://github.com/silverstripe-labs/silverstripe-travis-support.git ~/travis-support
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
- "if [ \"$BEHAT_TEST\" = \"\" ] && [ \"$CMS_TEST\" = \"\" ]; then php ~/travis-support/travis_setup.php --source `pwd` --target ~/builds/ss; fi"
- "if [ \"$BEHAT_TEST\" = \"1\" ] && [ \"$CMS_TEST\" = \"\" ]; then php ~/travis-support/travis_setup.php --source `pwd` --target ~/builds/ss --require silverstripe/behat-extension; fi"
- "if [ \"$BEHAT_TEST\" = \"\" ] && [ \"$CMS_TEST\" = \"1\" ]; then php ~/travis-support/travis_setup.php --source `pwd` --target ~/builds/ss --require silverstripe/cms:$CORE_RELEASE.x-dev; fi"
- "if [ \"$BEHAT_TEST\" = \"1\" ] && [ \"$CMS_TEST\" = \"1\" ]; then php ~/travis-support/travis_setup.php --source `pwd` --target ~/builds/ss --require silverstripe/behat-extension,silverstripe/cms:$CORE_RELEASE.x-dev; fi"
Fixed bugs in Travis CI set-up
2012-08-14 06:11:37 +02:00
- cd ~/builds/ss
Running Travis+Behat through Selenium, save artifacts
2013-10-16 14:01:14 +02:00
- php ~/travis-support/travis_setup_selenium.php --if-env BEHAT_TEST
- php ~/travis-support/travis_setup_php54_webserver.php --if-env BEHAT_TEST
Added support for Travis CI
2012-08-14 06:02:12 +02:00
Test against php 7
2015-02-26 02:32:47 +01:00
script:
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
- "if [ \"$BEHAT_TEST\" = \"\" ] && [ \"$CMS_TEST\" = \"\" ]; then vendor/bin/phpunit framework/tests; fi"
- "if [ \"$BEHAT_TEST\" = \"\" ] && [ \"$CMS_TEST\" = \"\" ]; then vendor/bin/phpunit framework/admin/tests; fi"
- "if [ \"$BEHAT_TEST\" = \"1\" ] && [ \"$CMS_TEST\" = \"\" ]; then vendor/bin/behat @framework; fi"
- "if [ \"$BEHAT_TEST\" = \"\" ] && [ \"$CMS_TEST\" = \"1\" ]; then vendor/bin/phpunit cms/tests; fi"
- "if [ \"$BEHAT_TEST\" = \"1\" ] && [ \"$CMS_TEST\" = \"1\" ]; then vendor/bin/behat @cms; fi"
Proof-of-concept of running Firefox Behat in Travis-CI
2013-10-02 05:04:31 +02:00
after_failure:
Move travis env vars out of .travis.yml and into travis CI dashboard
2016-12-06 22:31:09 +01:00
- php ~/travis-support/travis_upload_artifacts.php --if-env BEHAT_TEST,ARTIFACTS_KEY --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
Reference in New Issue Copy Permalink