-
Notifications
You must be signed in to change notification settings - Fork 10
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
add current and future ruby to travis #1040
Conversation
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.
👍
1bdf6bb
to
fada8b8
Compare
Gemfile.lock
Outdated
@@ -576,4 +576,4 @@ DEPENDENCIES | |||
wicked | |||
|
|||
BUNDLED WITH | |||
1.17.3 | |||
2.0.1 |
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.
The rpm build environment Henry was using for another project (cwrc_preservation) was having trouble with Bundler v2. Maybe check with him before merging.
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.
👍
3d33ce6
to
9cb6709
Compare
This application currently runs in production with Ruby 2.4. Some of our other application run with 2.5 and 2.6 is the newest. We can use travis to smoke test whether or not the changes we make are future compatible.
The con of this is that we're more likely to be caught in the flapping tests.