well... I finally figured it out and am sharing in hopes it helps someone spinning their wheels as I have on this...
--- Jamis Buck replied and got me on track to my solution. His suggestion to upgrade cap to 2.4 was a good one because there's a new -d switch for debugging. Using the -d switch gave me more info and a hint... one thing led to another and I ended up on a page of Jamis's (http:// weblog.jamisbuck.org/2007/10/14/capistrano-2-1) from the release for cap 2.1 and by reading the section entitled "No default PTY" I realized I was missing something in my capfile... specifically, the following line: default_run_options[:pty] = true I don't know how things worked for the last 5 months without it... and I still dont know what changed that broke things last week, but I can live with the magic that adding it "back" in did for me. sweet! thanks for the help Jamis and Jamie. On Jun 22, 1:57 pm, Jamis Buck <[EMAIL PROTECTED]> wrote: > You might want to try upgrading to a more recent capistrano, too. > 2.0.0 was a first cut at a major rewrite, and had many bugs (some > relating to displaying error messages). That said, subsequent releases > have had their bugs, too, so you kind of have to choose your poison. :( > > - Jamis > > On Jun 19, 2008, at 5:57 PM, lunaclaire wrote: > > > > > 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 -~----------~----~----~----~------~----~------~--~---
