Capistrano的轨道跳过任务`部署：更新”，因为它以前被调用

Question

我使用RVM轨，

使用Capistrano的deplying当我得到以下错误：

Skipping task `deploy:updating'. 
Capistrano tasks may only be invoked once. Since task `deploy:updating' was previously invoked, invoke("deploy:updating") at /home/ziaulrehman/.rvm/gems/ruby-2.3.4/gems/capistrano-3.8.2/lib/capistrano/tasks/framework.rake:64 will be skipped. 
If you really meant to run this task again, first call Rake::Task["deploy:updating"].reenable 
THIS BEHAVIOR MAY CHANGE IN A FUTURE VERSION OF CAPISTRANO. Please join the conversation here if this affects you. 
https://github.com/capistrano/capistrano/issues/1686 

我capfile有：

require 'capistrano/setup' 
require 'capistrano/deploy' 
require 'capistrano/bundler' 
require 'capistrano/rails' 
require 'rvm1/capistrano3' 
require 'capistrano/puma' 
require 'capistrano/sidekiq' 
install_plugin Capistrano::Puma 
install_plugin Capistrano::Puma::Nginx 

require "capistrano/scm/git" 
install_plugin Capistrano::SCM::Git 

require "capistrano/rails/assets" 
# there are no customm tasks 
Dir.glob("lib/capistrano/tasks/*.rake").each { |r| import r } 

而且我deploy.rb看起来像：

# config valid only for current version of Capistrano 
lock "3.8.2" 

set :application,  "webapp" 
set :deploy_via,  :remote_cache 
set :keep_releases, 5 
set :repo_url,  "git@github.com:org/webapp.git" 

append :linked_files, 'config/database.yml', 'config/secrets.yml', '.env.generic' 
append :linked_dirs, 'vendor/bundle', 'public/uploads' 

# Default deploy_to directory is /var/www/my_app_name 
set :deploy_to,  "/home/deployer/www/webapp" 

set :rvm1_ruby_version, 'ruby-2.3.4' 
# set :rvm_type, :user 
# set :default_env,  { rvm_bin_path: '~/.rvm/bin' } 
# fetch(:default_env).merge!(rvm_path: '~/.rvm/bin') 
set :rvm1_map_bins, -> { fetch(:rvm_map_bins).to_a.concat(%w{rake gem bundle ruby foreman}).uniq } 

before 'deploy', 'rvm1:install:ruby' 

set :sidekiq_processes => 2 
set :keep_assets, 2 
set :sidekiq_config => '#{release_path}/config/sidekiq.yml' 

set :pty, true 

我绝对没有自定义任务什么的，这些都是我使用所有的宝石，我怀疑某种宝石中的冲突。

如果有人能指出确切位置正在创建这个问题，我怎么能解决这个问题，将是巨大的。另外，我想知道这个问题的含义。一切似乎现在正常工作。

Answer 1

这是造成rvm1-capistrano3宝石的问题。我刚刚看了一下在GitHub上创业板的源代码，它是做奇怪的事情像注册挂钩这样的：

before :ruby, "deploy:updating" 

这是没有意义的我。这意味着，如果你在部署（由README建议）的开头援引rvm1:install:ruby，那么它会触发deploy:updating之前，你的部署，甚至还开始。通常应该在部署的端处触发。这个宝石的工作原理是令人惊讶的。

的Skipping task警告是非常重要的。你的部署可能会奏效，但它仍然令人担忧。我建议找到rvm1-capistrano3宝石的替代品。