bundle cache pulling the latest commit from master branch for a private hosted gem when gemfile.lock points to a different commit

Question

Why does the bundle cache pulling the latest commit from a privately hosted git based gem. The gemfile.lock is pointing to a different commit hash in it. Why is it not respecting the gemfile.lock ?

GIT
  remote: git@gitlab.xxxxx.de:projs/services-base.git
  revision: cdfc570585c7b9c48af49c9105bb304abfbfcf70
  branch: master
  ....

I am using the following configuration

bundle config set --local cache_path 'vendor/cache'
bundle config set --local cache_all 'true'
bundle config set --local cache_all_platforms 'true'
bundle config set --local allow_offline_install 'true'

I have set the update_sources in the gemrc configuration. The gem env gives

- GEM CONFIGURATION:
      - :update_sources => false
      - :verbose => true
      - :backtrace => false
      - :bulk_threshold => 1000
      - "config_file_name" => "/home/appuser/.gemrc"
      - "install" => "--no-document"
      - "update" => "--no-document"

RUBYGEMS VERSION: 3.3.3

RUBY VERSION: 3.1.0 (2021-12-25 patchlevel 0) [x86_64-linux]

BUNDLER VERSION: 2.3.13

It is not even respecting the gemrc configuration. Am I missing something here ? I am building a docker image for an app. (if that helps)

bundle cache pulling the latest commit from master branch for a private hosted gem when gemfile.lock points to a different commit

0 Answers0