-
Notifications
You must be signed in to change notification settings - Fork 18
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
You can't currently specify GEM_REPOS if the TEST_REPO doesn't already define the gem as a direct dependency. #36
Comments
I wonder if this is a bug here or with bundler-inject. @jrafanie Can you do an override_gem in manageiq locally? |
Oh I think I know what's going on...now that we made this a gem, the bundler context is part of the manageiq-cross_repo itself. I'll see what I can do with that. |
Seems to be that bundler-inject can't support transient dependencies - ManageIQ/bundler-inject#11 For now we may have to use ensure_gem instead. @agrare Thoughts? |
Yeah ensure_gem is how I've worked around this in the past, I'll test using it here as a general workaround |
Yeah with ensure_gem this works
|
And, you know, it actually overrides it which is a plus
|
If a gem isn't directly referenced in the core-repo's gemfile it cannot be overridden, ensure_gem has to be used. Fixes ManageIQ#36
If a gem isn't directly referenced in the core-repo's gemfile it cannot be overridden, ensure_gem has to be used. Fixes ManageIQ#36
If a gem isn't directly referenced in the core-repo's gemfile it cannot be overridden, ensure_gem has to be used. Fixes ManageIQ#36
Situation:
If I want to test cross repos with:
manageiq with memoist 0.16.0 dependency...
azure-armrest with memoist 0.16.0 dep.
It looks like any TEST_REPO that doesn't already specify azure-armrest as a gem can't override that gem. It assumes we need to do override_gem.
https://travis-ci.org/jrafanie/manageiq-cross_repo-tests/jobs/601518344#L311
The text was updated successfully, but these errors were encountered: