Capistrano fails to update code when pushed to prod

[newguy]

Hey guys
I am facing this problem every now and then and I have a work around
for this problem but still I want to know why this is happening.
Some times Capistrano deploy simply fails to fetch new code from the
SVN repository, it does a svn update -q of the local cache(which is a
directory in the /tmp folder) but it never updates the code and hence
the changed files never get propagated to the destination machines.

In order to fix this I manually delete the local cache and then do a
cap deploy:setup which makes these directories again and after that
when I do a deploy it doesn't do a svn update it simply does a svn
checkout and we get all the changed files and update code is pushed.

Can anyone throw more light on this behavour of Capistrano or suggest
me better ways to go about this problem.

Thanks

[Lee Hambley]

@newguy,

Can anyone throw more light on this behavour of Capistrano or suggest

me better ways to go about this problem.

Use Git. There's fewer and fewer good reasons to use SVN these days, and I haven't touched Subversion in years, I'd recommend switching to more modern source control system. (or of course stop using the remote cache).

This isn't a known issue with SVN, nor is it anything that has cropped up on the mailing list/support communities before, so I have to assume it's something specific to your environment.

- Lee (sorry that's probably not the answer you were looking for)