-
Notifications
You must be signed in to change notification settings - Fork 69
Ruby 2.5.7 support #36
Comments
So Github just announced that Actions will be GA on 13 November, anyone able to chime in on whether this will be available by then? |
I need ruby 2.6.5, and unless we can get support for that then unfortunately it's a no-go from the offset. I think this is going to be a pretty ubiquitous requirement for any serious app. 🙏 |
Hej! I built https://github.com/clupprich/ruby-build-action over the weekend, which makes use of ruby-build to install exactly the version of Ruby you need. While that sounds (and actually is) slow, you can use the actions/cache action to cache the Ruby installation in your workflows (which brings the time it takes to setup Ruby down to ~30 seconds). Let me know if that works for you. Feeback/issue reports/contributions welcome! |
@clupprich That absolutely solved this for me, and I imagine it will do so for many others! Great job. |
Thanks @clupprich...that worked perfectly! Not sure how useful setup-ruby is when you can't specify the exact ruby version you need. |
Not that everyone is testing on Windows, but I created MSP-Greg/actions-ruby, which installs current Ruby versions (along with ruby-head/master) and allows updating the gcc build tools/packages on Windows. Ruby 2.3.3 is also available, but if used for extension gems, it compiles with the newer 'DevKit'... |
+1 for Ruby 2.5.7 support. |
+1 |
I think this requires an update to the virtual environment, so I’ve requested it here: actions/runner-images#95 |
What are the currently supported Ruby versions? Our actions started failing today with a similar message, The support page linked by @konradpabjan in actions/setup-python#15 (comment) still says that Ruby 2.5.5 is supported. |
Ruby 2.5.5 should work. Just tested it out: Looking at the tools cache where the Ruby gets downloaded from, I still see version 2.5.5. It gets added here and automatically documented: https://github.com/actions/virtual-environments/blob/9786a9946a6db1a8d0c89948550753f9e01007b3/images/linux/scripts/installers/1804/hosted-tool-cache.sh#L39 If there are issues with the documented versions then |
2.5.5 is working for us again today. Thanks for testing it. |
Closing since 2.5.5 is working and there's already a tracking item in virtual-environments. Note a related issue: #44 |
2.5.7 is now available, and 2.5.5 has been removed. |
See #49 - flushing out ideas I have a prototype working locally where we download JIT from rvm if it's not already in the VM cache. I will have an experimental ref soon. The plan is to fall back ruby-build after that (which also has the benefits of self-hosted runners). @clupprich - I may pull inspiration from yours and/or you can have a look at my experimental branch. The ADR proposes using factored out caching logic (lib) so the consumer doesn't have to do the caching (probably just a bool option). Note that if self-hosted, it would only be slow the first build. |
Updating our ruby version, but now with actions our CI is unable to use the latest 2.5.x Ruby to run tests etc.
https://www.ruby-lang.org/en/news/2019/10/01/ruby-2-5-7-released/
The text was updated successfully, but these errors were encountered: