Install the current Bundler in Dockerfile

[smaboshe]

In Dockerfile, we have been specifying the exact Bundler version to install. This is no longer necessary.

This commit updates Dockerfile to install the current version of Bundler. Bundler will then take care of setting up the correct version to use.

Ref:

• Update Bundler to version 2.5.6 ruby#1635 (comment)

[github-actions]

Hello. Thanks for opening a PR on Exercism 🙂

We ask that all changes to Exercism are discussed on our Community Forum before being opened on GitHub. To enforce this, we automatically close all PRs that are submitted. That doesn't mean your PR is rejected but that we want the initial discussion about it to happen on our forum where a wide range of key contributors across the Exercism ecosystem can weigh in.

You can use this link to copy this into a new topic on the forum. If we decide the PR is appropriate, we'll reopen it and continue with it, so please don't delete your local branch.

If you're interested in learning more about this auto-responder, please read this blog post.

---

Note: If this PR has been pre-approved, please link back to this PR on the forum thread and a maintainer or staff member will reopen it.

[kotp]

This is no longer necessary.

It is is likely necessary. Knowing the version we are requiring gives a lot of information. Having a possible "latest version" does not let us brace against breaking changes, for example.

We should specify the version, and it should allow us to cache information as well. Including using bundle _x.x.x_ install --local if we end up caching the gems as well. (Speed for spinning up while having some flexibility, the cost being storage vs network transfer).

[Hunk13]

In my opinion, it would be great to parse the bundler version from Gemfile.lock and pass it into gem install bundler command like this.

RUN gem install bundler -v "$(grep -A 1 "BUNDLED WITH" Gemfile.lock | tail -n 1)"

in this case we will be sure that the bundler version is the same as in Gemfile.lock file.

[ErikSchierboom]

RUN gem install bundler -v "$(grep -A 1 "BUNDLED WITH" Gemfile.lock | tail -n 1)"

That sounds gopd. Could you update the PR?

[smaboshe]

That sounds gopd. Could you update the PR?

Done.

[smaboshe]

Thank you for merging this PR.

I see that it was reverted.

Would it be possible to have context for the revert? Did this break CI or deployment?

I can't seem to find any background for the revert here or in the discussion forum.

[smaboshe]

I have been able to find some context:

• Ruby Test Runner Down - Review Exercism Forum Post #145
• https://forum.exercism.org/t/ruby-test-runner-broken-chess-game-in-ruby-screenshots-included/10147

What tools are available that would have allowed me to see this issue earlier?

[kotp]

I have been able to find some context:

• Ruby Test Runner Down - Review Exercism Forum Post #145
• https://forum.exercism.org/t/ruby-test-runner-broken-chess-game-in-ruby-screenshots-included/10147

What tools are available that would have allowed me to see this issue earlier?

Subscribing to forum, the Ruby category, would have probably given you some indication early.

Subscribing to the github notifications for projects can be another way for timely notifications.

[ErikSchierboom]

I've reverted the revert :)

[smaboshe]

Thank you, @ErikSchierboom.

I imagine that you are able to see that things are working from your end. If this PR breaks things, I would be interested to know what the issue is. Thanks again!

[smaboshe]

Subscribing to forum, the Ruby category, would have probably given you some indication early.

Subscribing to the github notifications for projects can be another way for timely notifications.

Thank you, @kotp. I have subscribed to these.

[iHiD]

If this PR breaks things, I would be interested to know what the issue is.

It didn't. I basically just reverted anything merged in the last 24 hours to get things back to a working state. I should probably have commented, but it was late at night, urgent, and I knew Erik would tidy up my mess today so I was lazy :)