Thank-you for teaching this course, Stephen (and for what I've learned so far).
The feedback from travis-ci was a bit of a surprise, failing the .yaml file we provided. The job log did indicate tests passing locally.
I can't imagine we pushed a flawed .yaml, but does build config validation show that new conditions were added to travis since you published ch. 7?
root: deprecated key sudo (The key sudo has no effect anymore.)"
root: missing os, using the default linux
root: missing language, using the default ruby
It would be useful to know why the job log shows that Ruby is not finding the gemfile. Thanks again.
Thank-you for teaching this course, Stephen (and for what I've learned so far).
The feedback from travis-ci was a bit of a surprise, failing the .yaml file we provided. The job log did indicate tests passing locally.
I can't imagine we pushed a flawed .yaml, but does build config validation show that new conditions were added to travis since you published ch. 7?
root: deprecated key sudo (The key
sudohas no effect anymore.)"root: missing os, using the default linux
root: missing language, using the default ruby
It would be useful to know why the job log shows that Ruby is not finding the gemfile. Thanks again.