-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A handful of fixes to make the Cheffish matrix pass on all the relevant Chef versions. #68
Conversation
@@ -15,7 +16,8 @@ env: | |||
- CHEF_VERSION=12.4.1 | |||
- CHEF_VERSION=12.3.0 | |||
- CHEF_VERSION=12.2.1 | |||
- CHEF_VERSION=12.1.2 | |||
# - CHEF_VERSION=12.2.0 | |||
# - CHEF_VERSION=12.1.2 # known broken for now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did the allow_failures
block not work for these? I would think we still want it testing and showing up as failures (unless its taking a lot of time or something)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll clean that up: I'm thinking we don't need 12.2.0 if we've got 12.2.1, and 12.1.2 is broken but we can run it anyway. I'll also re-add Ruby versions to test against.
I have 1 question but 👍 and feel free to merge after answering that |
- Add .rspec, add chef-client-versions.gemfile.lock to .gitignore.
…ith Chef < 12.4.
…to us (e.g. for have_updated).
# - 2.0.0 | ||
# - 2.1.1 | ||
- 2.1.2 | ||
- 2.0.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not required for this checkin; but if you just say 2.0
and 2.1
, I think Travis will pick the latest.
👍 |
A handful of fixes to make the Cheffish matrix pass on all the relevant Chef versions.
No description provided.