[Feedback] Make an explicit mention of running with Ruby2.2 or 2.1 in documentation
I realise that living on bleeding edge (Ruby 2.3) implies bleeding but perhaps some folks can be spared from some head scratching time if they knew Ruby 2.3 will cause gitlab to malfunction with no apparent error.
In my case, project creation kept failing with error pointing towards gitlab-shell but bin/check kept passing and it took me a while to realise that in a recent update ruby 2.3 got installed. Sure enough when I went into /home/git/gitlab/vendor/bundle some gems were under ruby23 while others were under ruby22 (even on a fresh bundle reinstall).
I have no idea how this actually affects in reality (never used ruby myself) but after I restricted the system installation to ruby 2.2, things went back to normal.
Activity
cc @axil
Added ruby label
Relevant issue https://gitlab.com/gitlab-org/gitlab-ce/issues/3514
Reassigned to @axil
Milestone changed to 8.5
mentioned in merge request !2524 (merged)
-
In fact, ruby 2.2 was failing on some tests afaik that's why we are not currently supporting it. I created https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/2524 which adds a note in installation.md and requirements.md.
Status changed to closed by commit 41d22a1f
mentioned in commit 41d22a1f
-
@maverik There will be support for ruby 2.2 and 2.3 in GitLab 8.5. I marked all related issues with the ruby tag https://gitlab.com/gitlab-org/gitlab-ce/issues?label_name=ruby.
Many thanks Achilleas. As such I've been running in a side by side ruby installation of ruby 2.1 & 2.2 (with 2.2 as default profile) for months now and haven't had any issues. It was only yesterday when you mentioned that some tests are failing with 2.2 that I got to know why you don't officially mention 2.2.
Thank you for all the hard work as usual :)
