build: set gem location as vendor/bundle #1289
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The gitignore file already has
vendor/bundleignored - a common location to install gems.Without a sane default set - folks like me who are trying to learn all the pipelines cannot effectively run them. Take this example of running
bundle exec fastlane update_docson main fastlane repo.Ultimately after fastlane clones a new docs repo it executes this.
Which of course fails because the default gem location for this system at least is not in a user-land area - its system.
I'm under strong belief projects should declare where gems should be stored so alignment between local usage, CI usage and command usage can all depend on a specific setup. A simple
bundle updatehard-coded requires the end user to preconfigure environment variables or more - when the project should decide that.