pgbackrest/.travis.yml

branches:
  only:
    - integration
    - /-ci$/

dist: trusty
sudo: required

language: c

services:
  - docker

matrix:
  include:
    - env: PGB_CI="test --vm=u12"
    - env: PGB_CI="test --vm=f30 --param=no-package --param=c-only"
    - env: PGB_CI="test --vm=co6 --param=module=mock --param=module=real"
    - env: PGB_CI="test --vm=u18 --param=container-only"
    - env: PGB_CI=" doc --vm=u18"
    - env: PGB_CI="test --vm=co7 --param=module=mock --param=module=real"
    - dist: bionic
      env:
        - PGB_CI="test --vm=none --param=tz=America/New_York"
      services:
    - env: PGB_CI=" doc --vm=co6"
    - env: PGB_CI=" doc --vm=co7"

install:
  - umask 0022 && cd ~ && pwd && whoami && umask && groups
  - df -Th && top -bn1

script:
  - ${TRAVIS_BUILD_DIR?}/test/travis.pl ${PGB_CI?}
Continuous integration using travis-ci. 2017-02-21 08:59:23 -05:00			`branches:`
			`only:`
			`- integration`
			`- /-ci$/`

			`dist: trusty`
			`sudo: required`

			`language: c`

			`services:`
			`- docker`

Allow most unit tests to run outside of a container. Three major changes were required to get this working: 1) Provide the path to pgbackrest in the build directory when running outside a container. Tests in a container will continue to install and run against /usr/bin/pgbackrest. 1) Set a per-test lock path so tests don't conflict on the default /tmp/pgbackrest path. Also set a per-test log-path while we are at it. 2) Use localhost instead of a custom host for TLS test connections. Tests in containers will continue to update /etc/hosts and use the custom host. Add infrastructure and update harnessCfgLoad*() to get the correct exe and paths loaded for testing. Since new tests are required to verify that running outside a container works, also rework the tests in Travis CI to provide coverage within a reasonable amount of time. Mainly, break up to doc tests by VM and run an abbreviated unit test suite on co6 and co7. 2019-10-08 12:06:30 -04:00			`matrix:`
			`include:`
Update last tests that required sudo. All tests should now run in a sudo-less environment. 2019-10-16 17:05:24 +02:00			`- env: PGB_CI="test --vm=u12"`
Allow parameters to be passed to travis.pl. This makes configuring tests easier. Also add a parameter for tests that require sudo. This should be retired at some point but some tests still require it. 2019-10-15 17:19:42 +02:00			`- env: PGB_CI="test --vm=f30 --param=no-package --param=c-only"`
Add mock module to CentOS6/7 Travis CI testing. This was dropped at some point but is important for integration coverage. 2019-11-16 09:38:42 -05:00			`- env: PGB_CI="test --vm=co6 --param=module=mock --param=module=real"`
Update last tests that required sudo. All tests should now run in a sudo-less environment. 2019-10-16 17:05:24 +02:00			`- env: PGB_CI="test --vm=u18 --param=container-only"`
Allow parameters to be passed to travis.pl. This makes configuring tests easier. Also add a parameter for tests that require sudo. This should be retired at some point but some tests still require it. 2019-10-15 17:19:42 +02:00			`- env: PGB_CI=" doc --vm=u18"`
Add mock module to CentOS6/7 Travis CI testing. This was dropped at some point but is important for integration coverage. 2019-11-16 09:38:42 -05:00			`- env: PGB_CI="test --vm=co7 --param=module=mock --param=module=real"`
Allow most unit tests to run outside of a container. Three major changes were required to get this working: 1) Provide the path to pgbackrest in the build directory when running outside a container. Tests in a container will continue to install and run against /usr/bin/pgbackrest. 1) Set a per-test lock path so tests don't conflict on the default /tmp/pgbackrest path. Also set a per-test log-path while we are at it. 2) Use localhost instead of a custom host for TLS test connections. Tests in containers will continue to update /etc/hosts and use the custom host. Add infrastructure and update harnessCfgLoad*() to get the correct exe and paths loaded for testing. Since new tests are required to verify that running outside a container works, also rework the tests in Travis CI to provide coverage within a reasonable amount of time. Mainly, break up to doc tests by VM and run an abbreviated unit test suite on co6 and co7. 2019-10-08 12:06:30 -04:00			`- dist: bionic`
Allow parameters to be passed to travis.pl. This makes configuring tests easier. Also add a parameter for tests that require sudo. This should be retired at some point but some tests still require it. 2019-10-15 17:19:42 +02:00			`env:`
Allow timezones to be explicitly set for testing. The TZ environment variable was not reliably pushed down to the test processes. Instead pass TZ via a command line parameter and set explicitly in the test process. 2019-12-11 22:11:04 -05:00			`- PGB_CI="test --vm=none --param=tz=America/New_York"`
Disable docker service for --vm=none test. Starting this service wastes time and this will help catch any regressions where containers are being built when they should not be. 2019-10-10 11:28:37 -04:00			`services:`
Allow parameters to be passed to travis.pl. This makes configuring tests easier. Also add a parameter for tests that require sudo. This should be retired at some point but some tests still require it. 2019-10-15 17:19:42 +02:00			`- env: PGB_CI=" doc --vm=co6"`
			`- env: PGB_CI=" doc --vm=co7"`
Continuous integration using travis-ci. 2017-02-21 08:59:23 -05:00
			`install:`
Add disk/mem info for Travis. This is helpful for determining the virtual machine resources. 2019-10-13 14:02:52 -04:00			`- umask 0022 && cd ~ && pwd && whoami && umask && groups`
			`- df -Th && top -bn1`
Continuous integration using travis-ci. 2017-02-21 08:59:23 -05:00
			`script:`
Be smarter about which packages are loaded for testing. Now that our tests are more diversified it makes sense to load only the packages that are needed for each test. Move the package loads from .travis.yaml to test/travis.pl where we have more control over what is loaded. 2019-10-08 18:56:55 -04:00			`- ${TRAVIS_BUILD_DIR?}/test/travis.pl ${PGB_CI?}`