Skip to content

Set bundle path when Gemfile path is configured.

What does this MR do?

Config bundle path under project root, which is /srv/gitlab/vendor/bundle, when we use Gemfile in the sub-directories.

In !770 (merged) we added a variable to make it possible to adopt Gemfile in subdiretories, and it passed build. However, recently when I made another mirroring repo of CNG, I found that the job of building webservice failed, because the script clean-up-gems could not find directory /srv/gitlab/vendor/bundle/ruby. Actually bundle made another vendor folder under Gemfile subdirectory, which was /srv/gitlab/jh/vendor/bundle/ruby in our case.

Maybe the runner cache made the previous build success because it failed after I cleaned the runner cache our in dev environment.

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