db/pgbackrest
1
0
Fork 0
mirror of https://github.com/pgbackrest/pgbackrest.git synced 2024-12-12 10:04:14 +02:00
Code Issues Releases Activity
64c6102a15
pgbackrest/.travis.yml

34 lines
602 B
YAML
Raw Normal View History

Continuous integration using travis-ci.
2017-02-21 15:59:23 +02: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 18:06:30 +02:00
matrix:
include:
- env: PGB_CI="--vm=u12 test"
Add gcc 9 support. A number of tests have been updated and Fedora 30 has been added to the test suite so the unit tests can run on gcc 9. Stop running unit tests on co6/7 since we appear to have ample unit test coverage.
2019-10-09 21:03:03 +02:00
- env: PGB_CI="--vm=f30 test"
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 18:06:30 +02:00
- env: PGB_CI="--vm=co6 test"
- env: PGB_CI="--vm=u18 test"
- env: PGB_CI="--vm=u18 doc"
Add gcc 9 support. A number of tests have been updated and Fedora 30 has been added to the test suite so the unit tests can run on gcc 9. Stop running unit tests on co6/7 since we appear to have ample unit test coverage.
2019-10-09 21:03:03 +02:00
- env: PGB_CI="--vm=co7 test"
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 18:06:30 +02:00
- dist: bionic
env: PGB_CI="--vm=none test"
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 17:28:37 +02:00
services:
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 18:06:30 +02:00
- env: PGB_CI="--vm=co6 doc"
Add gcc 9 support. A number of tests have been updated and Fedora 30 has been added to the test suite so the unit tests can run on gcc 9. Stop running unit tests on co6/7 since we appear to have ample unit test coverage.
2019-10-09 21:03:03 +02:00
- env: PGB_CI="--vm=co7 doc"
Continuous integration using travis-ci.
2017-02-21 15:59:23 +02:00
install:
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-09 00:56:55 +02:00
- umask 0022
- cd ~ && pwd && whoami && umask && groups
Continuous integration using travis-ci.
2017-02-21 15:59:23 +02: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-09 00:56:55 +02:00
- ${TRAVIS_BUILD_DIR?}/test/travis.pl ${PGB_CI?}
Reference in New Issue Copy Permalink