Is anyone using Capistrano 1.2 with CVS? If so, anyone willing to share what their set :repository line in the capistrano file looks like? The password in there is no longer being picked up so I can''t deploy to my test server. All that''s changed is my update from Capistrano 1.1 to 1.2. Thanks, Wes -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk -~----------~----~----~----~------~----~------~--~---
Trying to debug this... does anyone know how to make capistrano spit out details about what it''s doing? Wes -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk -~----------~----~----~----~------~----~------~--~---
I found this - totally embarrassed because I fixed it months ago but never submitted the patch (which I am totally doing right now). Basically, the "repository" line in the Capistrano config. file was not being used to query the CVS repository for the last commit time, which is needed to figure out what to pull out of the repository. In capistrano-1.2.0/lib/capistrano/scm/cvs.rb, in method cvs_log, it should look like this: def cvs_log(path,branch) `cd #{path || "."} && cvs -d #{configuration.repository} -q log -N -r#{branch}` end The "-d #{configuration.repository}" was missing. The #{configuration.repository} variable is used for all other interactions with CVS except for the first one, so this makes the behavior more consistent. Wes -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk -~----------~----~----~----~------~----~------~--~---
Seemingly Similar Threads
- Capistrano with CVS repository doesn''t seem to work
- I have a Capistrano 1.1 patch - where does it go?
- Capistrano only runs migration against production env?
- Capistrano/SwitchTower "current" dir deployment question
- Capistrano/SwitchTower: DB activity for deploy task?