Skip to content

Set env var BUNDLE_GEMFILE to make sure some ruby scripts get correct gemfile path

What does this MR do?

After the MR !770 (merged), we get the ability to specify the Gemfile path for rails based images. But we found that even if the bundle config file was present in the /srv/gitlab, some ruby scripts such as gitlab-rails/scripts/lib/checks/rails-depencies still failed to find correct gemfile and vendor. As a temperory fix, this MR forces to set the env var BUNDLE_GEMFILE in gitlab-rails, so that all bundle based command and scritps can find correct gemfile and vendor.

Related issues

Checklist

See Definition of done.

For anything in this list which will not be completed, please provide a reason in the MR discussion

Required

  • Merge Request Title, and Description are up to date, accurate, and descriptive
  • MR targeting the appropriate branch
  • MR has a green pipeline on GitLab.com

Expected (please provide an explanation if not completing)

  • Test plan indicating conditions for success has been posted and passes
  • Documentation created/updated
  • Integration tests added to GitLab QA
  • The impact any change in container size has should be evaluated

Merge request reports