Capistrano 2.6.x breaks while trying to deploy to Openminds servers (because of git submodules)

[jeroenj]

The latest version of Capistrano (2.6.x and probably higher too) break deployments while using git.

This is caused by set :git_enable_submodules, 1.

This is because capistrano has updated their git commands with their latest release. The current version of git on the servers (1.5.6.5) have a different syntax for git submodules. As long as you are not using git submodules and git on the server isn't updated to a later release (everything after 1.5.6 should work), you can add the following line at the end of your Capfile:

set :git_enable_submodules, false

If you are however using git submodules and git on your server isn't up-to-date, you should stick with Capistrano 2.5.x for now.

[BlakeLucchesi]

I can confirm this issue. The command that fails during the deploy is:

git submodule -q update --init --recursive

[jeroenj]

Indeed. You can try the workaround I've provided above.

Currently we're upgraden git on all our servers at @openminds so this problem will no longer occur.

[BlakeLucchesi]

Ya, I just downgraded my version of capistrano since its a local change as opposed to upgrading git on all my servers. (The git-core package hasn't been updated to 1.6.x for ubuntu 9.04).

For those coming from Google. Downgrading capistrano can be done like so:

$ gem uninstall capistrano -v 2.6.0

$ gem install capistrano -v 2.5.20

[jeroenj]

We've upgraded git on all our (recent) servers now. This gem now works with any capistrano release (tested with 2.5.x and 2.9.x).

[petervandenabeele]

Great, that should allow to try to use the built-in load 'deploy/assets' functionality in recent capistrano versions.