Skip to content
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

bugfix: adjust travis to work with chef12/ruby2 #73

Merged
merged 2 commits into from Feb 5, 2015
Merged

Conversation

arlimus
Copy link
Member

@arlimus arlimus commented Feb 5, 2015

for ruby 2.0 and greater, test with chef 11 and 12 (or greater). for ruby 1.9 (or before), don't test chef 12 as it requires ruby 2.0 to work:

https://www.chef.io/blog/2014/11/25/ruby-1-9-3-eol-and-chef-12/
Signed-off-by: Dominik Richter dominik.richter@gmail.com

for ruby 2.0 and greater, test with chef 11 and 12 (or greater). for ruby 1.9 (or before), don't test chef 12 as it requires ruby 2.0 to work:

https://www.chef.io/blog/2014/11/25/ruby-1-9-3-eol-and-chef-12/
Signed-off-by: Dominik Richter <dominik.richter@gmail.com>
Signed-off-by: Dominik Richter <dominik.richter@gmail.com>
@coveralls
Copy link

Coverage Status

Coverage increased (+6.77%) to 100.0% when pulling 3367ac6 on travis4ruby2+ into e071016 on master.

@coveralls
Copy link

Coverage Status

Coverage increased (+6.77%) to 100.0% when pulling 3367ac6 on travis4ruby2+ into e071016 on master.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage increased (+6.77%) to 100.0% when pulling 3367ac6 on travis4ruby2+ into e071016 on master.

chris-rock added a commit that referenced this pull request Feb 5, 2015
bugfix: adjust travis to work with chef12/ruby2
@chris-rock chris-rock merged commit 4953f40 into master Feb 5, 2015
@chris-rock
Copy link
Member

@arlimus thanks for this improvement

@arlimus arlimus deleted the travis4ruby2+ branch February 6, 2015 02:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants