Files
vagrant-libvirt/.travis.yml
Darragh Bailey 63f34432ad Allow dev with latest vagrant to use newer vagrant-spec (#1098)
Latest vagrant depends on a vagrant-spec release containing a more
recent dependency on childprocess than is supported for earlier releases
of vagrant.

Adjust dependencies to pin to the specific release of vagrant-spec if
the request version of vagrant is 2.2.7 or older.

Does not attempt to handle the situation where a version is specified
that cannot be parsed.

While it would be useful to test against newer versions of 2.2.x, it
appears this encounters a bug in upstream vagrant when installing in
dev mode see https://github.com/hashicorp/vagrant#11293
Therefore limit latest 2.2.x released version tested against to 2.2.4.
2020-04-23 09:12:04 +01:00

45 lines
971 B
YAML

---
language: ruby
dist: xenial
before_install:
- gem update --system --conservative || (gem i "rubygems-update:~>2.7" --no-document && update_rubygems)
- gem update bundler --conservative
addons:
apt:
packages: libvirt-dev
update: true
install: bundle install
script: bundle exec rspec --color --format documentation
notifications:
email: false
env:
global:
- NOKOGIRI_USE_SYSTEM_LIBRARIES=true
matrix:
- VAGRANT_VERSION=v2.0.4
- VAGRANT_VERSION=v2.1.5
- VAGRANT_VERSION=v2.2.4
- VAGRANT_VERSION=master
rvm:
- 2.2.10
- 2.3.5
- 2.4.10
- 2.6.6
matrix:
allow_failures:
- env: VAGRANT_VERSION=master
exclude:
- env: VAGRANT_VERSION=v2.0.4
rvm: 2.6.6
- env: VAGRANT_VERSION=v2.1.5
rvm: 2.6.6
- env: VAGRANT_VERSION=v2.2.4
rvm: 2.2.10
- env: VAGRANT_VERSION=v2.2.4
rvm: 2.3.5
- env: VAGRANT_VERSION=master
rvm: 2.2.10
- env: VAGRANT_VERSION=master
rvm: 2.3.5