Closed gwarf closed 5 years ago
So tests are failing while nothing related to them was (or should have been) changed on our side, previous build succeed: https://travis-ci.org/EGI-Foundation/ansible-style-guide/builds/515276999
So I restarted build 109 that was a success but now it fails, so really a change on Travis's side. We can probably merge and address this problem in another PR.
Testing if it's related to https://changelog.travis-ci.com/xenial-as-the-default-build-environment-99476 (errors seems to be using xenial instead of trusty)
OK, so it also fails with a trusty node...
Can you summarise your understanding of the problem right now for this rubber duck:
So currently bundler
is used to install inspec
(and there is no error during the installation phase), but inspec
is not found in $PATH
nor when using bundle exec
. It's the same for the new xenial
as for the previous trusty
build images. And builds that were previously succeeding are now failing, so it may be a problem on the build image side or on the bundle
/ gem
side.
OK, so now the build seems to be fix, a problem with the ruby version required by inspec/train. It seems that the ruby rvm version used to build the gems is >= 2.4
while the system version is < 2.3
and from inspec >= 4.3.2
ruby 2.4
is required. I'm trying to get caching to work for both ruby
and python
but now build are stale. Let's see and if everything is OK in the end we can squash the PR to clean the dirty bits.
OK, so now I stop, I tried using rvm
instead of system ruby but rvm install
builds fail silently. And bundler seems to be already provided by the travis image, as on the plain xenial it's required to install it after ruby-all
.
Using an old version of inspec is probably find for the time being and I don't have more time for this.
Fix permalinks for some documentation pages.