-
Notifications
You must be signed in to change notification settings - Fork 157
Remove Ruby container for 3.1. #618
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
Conversation
And remove references to that Ruby stream. That version is EOL.
Pull Request validationFailed🔴 Approval - missing or changes were requested Success🟢 CI - All checks have passed |
phracek
left a comment
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.
You have removed the version '3.1' completelly.
What about to update also these two conditions:
- https://github.com/sclorg/s2i-ruby-container/blob/master/test/conftest.py#L55
- https://github.com/sclorg/s2i-ruby-container/blob/master/test/run#L153
Just add '3.3' and more would be fine.
Wanted to keep that since its more of a "dependency" check, but it does mean that the related branch on rails-ex can be updated more freely with >= 3.3. Alright. |
|
I don't think we can change the 3.1 in bash, and I might've made a mistake when translating the bash here to python. The condition in The bash line is finnicky, I'd rather not edit it, and I'll fixup the python line. |
When translating the bash to python, the bash condition was '<= 3.1', not '< 3.1', therefore the range inversion is '> 3.1'. Since we also removed the 3.1, just bump it properly to '>= 3.3'.
|
Let's test it again. [test-all] |
Testing Farm results
|
phracek
left a comment
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.
LGTM. The PyTest failures I will solve later on.
And remove references to that Ruby stream.
That version is EOL.