Use setting to determine if test should be ran for full installation

CHANGELOG.md

@@ -1,6 +1,6 @@
 # [Unreleased][] (master)
 
-* Your contribution here!
+* Added `bundle_check_before_install` option to allow bypassing the `bundle install test` in the `bundler:install` task.
 
 # [1.5.0][] (23 Dec 2018)
 

README.md

@@ -80,6 +80,7 @@ set :bundle_without, %w{development test}.join(' ')             # this is defaul
 set :bundle_flags, '--deployment --quiet'                       # this is default
 set :bundle_env_variables, {}                                   # this is default
 set :bundle_clean_options, ""                                   # this is default. Use "--dry-run" if you just want to know what gems would be deleted, without actually deleting them
+set :bundle_check_before_install, true                          # default: true. Set this to false to bypass running `bundle check` before executing `bundle install`
 ```
 
 You can parallelize the installation of gems with bundler's jobs feature.

lib/capistrano/tasks/bundler.cap

@@ -28,7 +28,8 @@ namespace :bundler do
           options = []
           options << "--gemfile #{fetch(:bundle_gemfile)}" if fetch(:bundle_gemfile)
           options << "--path #{fetch(:bundle_path)}" if fetch(:bundle_path)
-          if test(:bundle, :check, *options)
+
+          if fetch(:bundle_check_before_install) && test(:bundle, :check, *options)
             info "The Gemfile's dependencies are satisfied, skipping installation"
           else
             options << "--binstubs #{fetch(:bundle_binstubs)}" if fetch(:bundle_binstubs)
@@ -84,5 +85,6 @@ namespace :load do
     set :bundle_jobs, 4
     set :bundle_env_variables, {}
     set :bundle_clean_options, ""
+    set :bundle_check_before_install, true
   end
 end