INFO [050fe961] Running mkdir -p /home/rails/rails-
capistrano/releases/20140114234157 on staging-rails
DEBUG [050fe961] Command: cd /home/rails/rails-capistrano/repo && ( PATH=/opt/ruby/bin:$PATH GIT_ASKPASS=/bin/echo GIT_SSH=/tmp/rails/git-ssh.sh mkdir -p /home/rails/rails-capistrano/releases/20140114234157 )
INFO [050fe961] Finished in 0.142 seconds with exit status 0 (successful).
INFO [2dea2fe5] Running git archive feature/Capistrano | tar -x -C /home/rails/rails-capistrano/releases/20140114234157 on staging-rails
DEBUG [2dea2fe5] Command: cd /home/rails/rails-capistrano/repo && ( PATH=/opt/ruby/bin:$PATH GIT_ASKPASS=/bin/echo GIT_SSH=/tmp/rails/git-ssh.sh git archive feature/Capistrano | tar -x -C /home/rails/rails-capistrano/releases/20140114234157 )
DEBUG [2dea2fe5] fatal: Not a valid object name
DEBUG [2dea2fe5] tar: This does not look like a tar archive
DEBUG [2dea2fe5] tar:
DEBUG [2dea2fe5] Exiting with failure status due to previous errors
我对两件事感到困惑:
git archive
:git archive feature/Capistrano | tar -x -C /home/rails/rails-capistrano/releases/20140114234157
tar
failing?发布于 2014-05-29 23:09:27
我也有同样的问题,直到我意识到我是在从git中拔出不存在的分支。
发布于 2014-05-28 00:55:27
删除app_name/repo也为我修复了这个问题。
发布于 2015-11-17 08:40:24
当要部署的服务器中的存储库混乱时,就会发生这种情况。我们讨论的是Capistrano在默认情况下会放在/var/www/$application/repo
中(供其他人参考)的git存储库。
在本例中,它没有本地功能/ |
分支,因此在运行git archive feature/Capistrano
时,不会向该Capistrano管道输出任何内容。要进行确认,请通过ssh进入服务器,通过cd进入/home/rails/rails-capistrano/repo,然后运行git branch
。
我可以想到两种可能的解决方案/方法来排除故障:
git remote -v
——您可能只需要在deploy中更新您的::repo_url
(并删除回购/目录)。https://stackoverflow.com/questions/21126518
复制相似问题