good thought, but it seems to give me even less info! now I get: cap deploy -v -S server=staging ** transaction: start *** [deploy:update_code] rolling back
...and then it cuts out. Also, I should mention that in regard to svn (if that's where the problem lies)... I can still commit and check out using my gui client (TortoiseSVN)... it just doesnt work when capistrano is trying to access it oh... and I'm on Windows Vista On Jun 19, 5:32 am, Jamie Orchard-Hays <[EMAIL PROTECTED]> wrote: > Start by adding -v (one or more) to your cap command and see if you > get some more info back. > > Jamie > On Jun 18, 2008, at 5:53 PM, lunaclaire wrote: > > > > > I'm suddenly having a problem deploying. I haven't changed anything in > > my deployment configuration (deploy.rb, svn repo, server configs) in > > about 5 months so I'm mystified about what's happened since my last > > successful deploy last nite. > > > I'm running capistrano 2.0.0. > > > here's what I get back: > > > * executing `deploy' > > * executing `deploy:update' > > ** transaction: start > > * executing `deploy:update_code' > > *** [deploy:update_code] rolling back > > * executing "rm -rf /var/www/apps/obc/releases/20080618193150; true" > > servers: ["staging.obc.com"] > > [staging.obc.com] executing command > > command finished > > > my guess is that because it's choking on the deploy:update_code, that > > it's something with my svn checkout...? > > > I can include the deploy.rb file if that's useful... > > > Any thoughts or ideas on how to tackle the problem solving on this? --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
