Hi Lee,It seems a sshd config limit; because those servers fails sometimes and succeed in other runs. I commented half my servers lists (leaving those which failed in the uncommented list) and they all passed.
Are you sure `:copy` bypasses the SCM? I'm seeing the following when I run cap deploy:
getting (via checkout) revision 59622948e8070cc3dc16852d977f8e33269117c8 to /tmp/20110521174820 executing locally: git clone -q [email protected]:gespro-v1.git /tmp/20110521174820 && cd /tmp/20110521174820 && git checkout -q -b deploy 59622948e8070cc3dc16852d977f8e33269117c8
command finished in 12863ms compressing /tmp/20110521174820 to /tmp/20110521174820.tar.gz executing locally: tar chzf 20110521174820.tar.gz 20110521174820 command finished in 3488ms servers: ["...."] ** sftp upload /tmp/20110521174820.tar.gz -> /tmp/20110521174820.tar.gzSo it seems :copy clones my repo in a temporary dir, then compresses it and uploads it to every server.
Best regards, Manuel. On 05/21/2011 11:17 AM, Lee Hambley wrote:
I think this may be related to some sshd limit in my git server. I'm deploy to more than 20 servers. I'm overcoming this by setting :deploy_via copy. Is this the recommended way to go? This is related to one of the machines not having keyed access to the Git server (so it's hanging up, because the key exchange failed) - the :copy strategy is viable… but deploys a tarball from your workstation to all hosts, bypassing SCM (so I don't advise it) If you deploy to more than 20 servers, and only two are failing, your situation should be easy to cure! -Lee
-- * You received this message because you are subscribed to the Google Groups "Capistrano" group. * To post to this group, send email to [email protected] * To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano?hl=en
<<attachment: manuelva.vcf>>
