Skip to content
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

Bring your own Ruby (whoops) #1000

Merged
merged 1 commit into from
Mar 20, 2023
Merged

Bring your own Ruby (whoops) #1000

merged 1 commit into from
Mar 20, 2023

Conversation

ryanmoran
Copy link
Contributor

Before the cflinuxfs4 stack becomes the default in CF, we will be removing the ruby interpreter from the set of installed packages. This means that the Java buildpack will need to bring its own interpreter in order to keep running on Ruby.

This PR contains a small bash shim that sits in front of each of the buildpack bin/* executables. The shim makes sure that there is an installed Ruby interpreter in a predefined location and then execs the equivalent Ruby entrypoint for the buildpack.

The buildpack packaging and configuration have been slightly modified to allow for this to work both online and offline.

The buildpack will run with the latest Ruby 3.1.x version available in the Ruby Buildpack repository.

@ryanmoran ryanmoran mentioned this pull request Mar 9, 2023
- the bin/{compile,detect,finalize,release} executables have been
  wrapped in a small shim that makes sure a Ruby interpreter is
  available on the PATH before exec-ing the existing buildpack
  entrypoints
- works both online and offline
- currently pinned to the latest Ruby 3.1.x version available in the
  Ruby Buildpack repository
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants