woocommerce/.travis.yml

language: php

sudo: false

# Test main supported versions of PHP against latest WP.
php:
  - 5.6
  - 7.0

env:
  - WP_VERSION=latest WP_MULTISITE=0

# Additional tests against stable PHP (min recommended version is 5.6) and past supported versions of WP
# and code coverage report.
matrix:
  fast_finish: true
  include:
  - php: 5.3
    dist: precise
  - php: 5.2
    dist: precise
  - php: 7.1
    env: WP_VERSION=latest WP_MULTISITE=0 RUN_PHPCS=1
  - php: 7.1
    env: WP_VERSION=latest WP_MULTISITE=0 RUN_CODE_COVERAGE=1
  allow_failures:
  - env: WP_VERSION=latest WP_MULTISITE=0 RUN_CODE_COVERAGE=1

before_script:
  - export PATH="$HOME/.composer/vendor/bin:$PATH"
  - bash tests/bin/install.sh woocommerce_test root '' localhost $WP_VERSION
  - bash tests/bin/travis.sh before

script:
  - bash tests/bin/phpunit.sh
  - bash tests/bin/phpcs.sh

after_script:
  - bash tests/bin/travis.sh after

# Specifies that Travis should create builds for master and release branches and also tags.
branches:
  only:
    - master
    - /^\d+\.\d+(\.\d+)?(-\S*)?$/
    - /^release\//
[#3176] Add unit test boostrap 2014-09-01 06:03:52 +00:00			`language: php`

Update travis config; remove 5.2, add 5.6 and hhvm 2015-02-03 16:43:01 +00:00			`sudo: false`

test tweak 2017-08-22 10:02:32 +00:00			`# Test main supported versions of PHP against latest WP.`
Update travis config; remove 5.2, add 5.6 and hhvm 2015-02-03 16:43:01 +00:00			`php:`
			`- 5.6`
Added PHP 7 in the tests 2015-12-08 18:26:14 +00:00			`- 7.0`
Update travis config; remove 5.2, add 5.6 and hhvm 2015-02-03 16:43:01 +00:00
			`env:`
Remove unused Travis environment variable This commit removes the unused Travis enrivonment variable PHP_LATEST_STABLE. 2017-11-13 19:22:46 +00:00			`- WP_VERSION=latest WP_MULTISITE=0`
Update travis config; remove 5.2, add 5.6 and hhvm 2015-02-03 16:43:01 +00:00
Generate code coverage report on a separate non-blocking Travis job Travis build is taking about 40 minutes to complete, and that is mostly because of the generation of the code coverage report. To address that, this commit changes Travis configuration to run the command to generate code coverage report on a separate non-blocking Travis job. This way once the jobs that run the tests finishes, Travisi will mark the build as successful and will keep running code coverage on a separate job. 2017-11-13 17:53:42 +00:00			`# Additional tests against stable PHP (min recommended version is 5.6) and past supported versions of WP`
			`# and code coverage report.`
[#3176] Add unit test boostrap 2014-09-01 06:03:52 +00:00			`matrix:`
Generate code coverage report on a separate non-blocking Travis job Travis build is taking about 40 minutes to complete, and that is mostly because of the generation of the code coverage report. To address that, this commit changes Travis configuration to run the command to generate code coverage report on a separate non-blocking Travis job. This way once the jobs that run the tests finishes, Travisi will mark the build as successful and will keep running code coverage on a separate job. 2017-11-13 17:53:42 +00:00			`fast_finish: true`
[#3176] Add unit test boostrap 2014-09-01 06:03:52 +00:00			`include:`
Travis 2017-07-20 10:23:37 +00:00			`- php: 5.3`
5.3 does not like dist 2017-07-20 14:55:45 +00:00			`dist: precise`
Travis 2017-07-20 10:23:37 +00:00			`- php: 5.2`
5.3 does not like dist 2017-07-20 14:55:45 +00:00			`dist: precise`
Don't run PHPCS on the code coverage Travis job PR #17680 added a new PHP 7.1 Travis build job to generate code coverage report. PHPCS was configured to run on all PHP 7.1 build jobs. So this means that after #17680 was merged, Travis started running PHPCS twice. This commit fixes this issue by setting a new environment variable called `$RUN_PHPCS` and using this variable, instead of the PHP version, to decide when to run PHPCS. 2017-11-21 20:09:07 +00:00			`- php: 7.1`
			`env: WP_VERSION=latest WP_MULTISITE=0 RUN_PHPCS=1`
Generate code coverage report on a separate non-blocking Travis job Travis build is taking about 40 minutes to complete, and that is mostly because of the generation of the code coverage report. To address that, this commit changes Travis configuration to run the command to generate code coverage report on a separate non-blocking Travis job. This way once the jobs that run the tests finishes, Travisi will mark the build as successful and will keep running code coverage on a separate job. 2017-11-13 17:53:42 +00:00			`- php: 7.1`
Remove unnecessary Travis environment variable PHP_LATEST_STABLE 2017-11-13 19:24:52 +00:00			`env: WP_VERSION=latest WP_MULTISITE=0 RUN_CODE_COVERAGE=1`
Generate code coverage report on a separate non-blocking Travis job Travis build is taking about 40 minutes to complete, and that is mostly because of the generation of the code coverage report. To address that, this commit changes Travis configuration to run the command to generate code coverage report on a separate non-blocking Travis job. This way once the jobs that run the tests finishes, Travisi will mark the build as successful and will keep running code coverage on a separate job. 2017-11-13 17:53:42 +00:00			`allow_failures:`
Remove unnecessary Travis environment variable PHP_LATEST_STABLE 2017-11-13 19:24:52 +00:00			`- env: WP_VERSION=latest WP_MULTISITE=0 RUN_CODE_COVERAGE=1`
[#3176] Add unit test boostrap 2014-09-01 06:03:52 +00:00
			`before_script:`
Travis 2017-09-26 12:24:11 +00:00			`- export PATH="$HOME/.composer/vendor/bin:$PATH"`
			`- bash tests/bin/install.sh woocommerce_test root '' localhost $WP_VERSION`
			`- bash tests/bin/travis.sh before`
[#3176] Add unit test boostrap 2014-09-01 06:03:52 +00:00
attempt to run PHPCS on travis 2016-08-27 14:18:14 +00:00			`script:`
Restored tests/bin/phpunit.sh 2017-10-05 16:09:39 +00:00			`- bash tests/bin/phpunit.sh`
Moved phpcs after phpunit 2017-10-10 13:50:22 +00:00			`- bash tests/bin/phpcs.sh`
Add coveralls.io for tracking test coverage 2014-09-07 18:53:33 +00:00
			`after_script:`
added .yml format in .editorconfig, closes #6364 2014-09-22 19:15:16 +00:00			`- bash tests/bin/travis.sh after`
Prevent Travis builds duplication This commit changes Travis configuration file to specify a list of branches that it should build. This way Travis will only create a new build when a commit is pushed to the master branch and release branches and when tags are created. The behavior for PRs is not modified and PR creation and updates will still trigger builds. Doing this to speed up Travis build by preventing it from running two builds for PR that are created from a branch of the same repository. Before this change, Travis would create a build when the branch is pushed to GitHub (continuous-integration/travis-ci/push) and another one when the PR is created (continuous-integration/travis-ci/pr). For an example, see https://github.com/woocommerce/woocommerce/pull/17680. 2017-11-20 19:18:29 +00:00
			`# Specifies that Travis should create builds for master and release branches and also tags.`
			`branches:`
			`only:`
			`- master`
			`- /^\d+\.\d+(\.\d+)?(-\S*)?$/`
			`- /^release\//`