Closed jacob-s-son closed 7 years ago
Are you sure you're vendoring both the https
and git
version of the git repo? Keep in mind bundler is not built to be resilient to those sort of changes in the Gemfile -- it can definitely cause things to require re-installation
@segiddins thanks for your reply. So you are saying that dependencies list for bundler looks wether it was bundled with HTTPS
or git
last time? All developers use SSH access, so the bundled version on the local machines is git
.
@segiddins thanks again for your help. It did not come into my mind, that this alters the remote key in Gemfile.lock
and as the result does not correspond to the committed Gemfile.lock
! Now that we know the issue, will workaround something. Thanks!
What you're trying to accomplish
Recently due to security warning, we switched our private dependencies to use HTTPS for fetching from Github. Since then bundle check is failing constantly on a particular dependency even if it's up-to date.
The command you ran
bundle check --path=vendor/bundle || bundle install --path=vendor/bundle --jobs=4 --retry=3
What you expected to happen
bundle install
would not be triggered.What actually happened
bundle install
was executed, printed the usual output, when no new dependencies are installed.The exception backtrace(s), if any
This is the error I get on every build:
Everything output by running bundle env
Other
git
and SSH key authentication. In that particular casebundle check
did not fail.bundle install
was run when building,bundle check
is passing. So it fails only on the first run ifbundle install
was not yet executed during the build.~/.bundler
andvendor/bundle
Maybe it is something that we are doing wrong, any suggestions are welcome, while the issue is not critical it is 1s vs 25s on our CI.