Support binarySource=install for bundler

[rarkins]

What would you like Renovate to be able to do?

Support runtime install of bundler when binarySource=install

If you have any ideas on how this should be implemented, please tell us here.

Currently we install bundler using gem install...:

renovate/lib/manager/bundler/artifacts.ts

Lines 124 to 127 in ec723e3

	const preCommands = [
	'ruby --version',
	`gem install bundler${bundlerVersion}`,
	];

We probably could run gem install into our full container, but maybe we should add install-tool bundler?

Is this a feature you are interested in implementing yourself?

Maybe

[viceice]

We should use install-tool for all to simplify code

[rarkins]

We are using install-gem for bundler: https://github.com/containerbase/buildpack/blob/26cf7d7273177157cfa1d09af62e8a8e8a189e83/test/ruby/Dockerfile#L65

Do you think we should add a install-tool wrapper for each "well-known" tool like this, or adapt our Renovate code to supply separate tool/gem/pip/npm lists? The challenge with that is ordering

[rarkins]

Blocked by containerbase/base#251

[viceice]

now unblocked

[rarkins]

Which versions of renovate/ruby images would support install-tool bundler ?

[rarkins]

Problem:

❯ docker run --rm -it renovate/ruby:2.6.4 /bin/bash
ubuntu@789553dfb959:/$ install-tool bundler 1.17.2
Installing tool bundler v1.17.2
Fetching bundler-1.17.2.gem
Successfully installed bundler-1.17.2
1 gem installed
Bundler version 1.17.2
ubuntu@789553dfb959:/$ bundle --version
bash: bundle: command not found
ubuntu@789553dfb959:/$ bundler --version
Bundler version 1.17.2
ubuntu@789553dfb959:/$ 

Renovate today calls bundle and not bundler. Not sure if we break anyone self-hosted if we switch to bundle from bundler

[renovate-release]

🎉 This issue has been resolved in version 31.52.0 🎉

The release is available on:

• GitHub release
• 31.52.0

Your semantic-release bot 📦🚀