composer/.travis.yml

language: php

sudo: false

cache:
  directories:
    - $HOME/.composer/cache

addons:
  apt:
    packages:
      - parallel

php:
  - 5.3.3
  - 5.3
  - 5.4
  - 5.5
  - 5.6
  - 7.0
  - hhvm
  - nightly

matrix:
  fast_finish: true
  allow_failures:
    - php: 7.0
    - php: nightly

before_script:
    - rm -f ~/.phpenv/versions/$(phpenv version-name)/etc/conf.d/xdebug.ini
    - flags=""
    - if [ `phpenv version-name` == "5.3.3" ]; then flags="--ignore-platform-reqs"; fi
    - composer install $flags
    - bin/composer install $flags
    - git config --global user.name travis-ci
    - git config --global user.email travis@example.com

script:
    - ls -d tests/Composer/Test/* | parallel --gnu --keep-order 'echo "Running {} tests"; ./vendor/bin/phpunit -c tests/complete.phpunit.xml --colors=always {} || (echo -e "\e[41mFAILED\e[0m {}" && $(exit 1));'

git:
  depth: 5
Add travis build file 2011-11-13 17:48:51 +00:00			`language: php`

Switch to the docker-based infrastructure on Travis 2015-03-04 15:48:39 +00:00			`sudo: false`

			`cache:`
			`directories:`
			`- $HOME/.composer/cache`

			`addons:`
Update the config of the apt addon to the new syntax 2015-08-20 11:02:17 +00:00			`apt:`
			`packages:`
			`- parallel`
Switch to the docker-based infrastructure on Travis 2015-03-04 15:48:39 +00:00
Allow the PHP5.5-build to fail PHP5.5 is not officially released, so making it part of the overall build-success seems not useful. It can be simply re-enabled it, when PHP5.5 is released, or as soon as the builds doesn't fail anymore. 2013-01-11 20:47:32 +00:00			`php:`
Add 5.3.3 builds to travis 2012-05-28 12:11:30 +00:00			`- 5.3.3`
Add travis build file 2011-11-13 17:48:51 +00:00			`- 5.3`
			`- 5.4`
Add 5.5 builds on travis 2012-12-20 12:59:21 +00:00			`- 5.5`
Run tests on PHP 5.6 on travis too 2014-02-24 07:24:01 +00:00			`- 5.6`
Added php7 to travis 2015-03-01 20:47:15 +00:00			`- 7.0`
Test HHVM on Travis-CI, allowing failures. 2013-12-19 15:33:37 +00:00			`- hhvm`
Update .travis.yml 2015-10-27 10:12:43 +00:00			`- nightly`
Test on HHVM nightly releases. Allow to fail. Nightly releases could change in unpredictable way. So they should not fail the whole build. However we could catch problems and breaking changes on next versions of HHVM early. 2015-03-08 17:30:56 +00:00
			`matrix:`
Report Travis CI build success early This will report the build has succceeded even if allowed to fail jobs are still running. See https://github.com/composer/composer/pull/3828. Docs: http://docs.travis-ci.com/user/build-configuration/#Fast-finishing Props to @fonsecas72. 2015-03-09 08:22:39 +00:00			`fast_finish: true`
Update .travis.yml 2015-10-27 10:12:43 +00:00			`allow_failures:`
allow 7.0 failures until travis fixes containers/stable release 2015-11-19 11:00:57 +00:00			`- php: 7.0`
Update .travis.yml 2015-10-27 10:12:43 +00:00			`- php: nightly`
Test HHVM on Travis-CI, allowing failures. 2013-12-19 15:33:37 +00:00
Add parallel build to travis script 2013-09-25 08:14:42 +00:00			`before_script:`
Test HHVM on Travis-CI, allowing failures. 2013-12-19 15:33:37 +00:00			`- rm -f ~/.phpenv/versions/$(phpenv version-name)/etc/conf.d/xdebug.ini`
Fix 5.3.3 build 2015-10-28 02:52:53 +00:00			`- flags=""`
			- if [ `phpenv version-name` == "5.3.3" ]; then flags="--ignore-platform-reqs"; fi
			`- composer install $flags`
			`- bin/composer install $flags`
Make sure git is setup to allow commits on travis 2013-03-28 11:48:19 +00:00			`- git config --global user.name travis-ci`
			`- git config --global user.email travis@example.com`
Update travis config 2011-11-13 18:01:46 +00:00
Add parallel build to travis script 2013-09-25 08:14:42 +00:00			`script:`
Update .travis.yml 2015-10-27 09:11:01 +00:00			`- ls -d tests/Composer/Test/* \| parallel --gnu --keep-order 'echo "Running {} tests"; ./vendor/bin/phpunit -c tests/complete.phpunit.xml --colors=always {} \|\| (echo -e "\e[41mFAILED\e[0m {}" && $(exit 1));'`

reduce commit history of git checkout (git depth 5) 2014-04-30 10:06:02 +00:00			`git:`
Fix the Travis configuration exit should not be used in script commands, because it exits the whole build script. Thus, turning a failure exit code into another failure exit code is not needed. 2014-12-02 10:39:01 +00:00			`depth: 5`