Donovan, Excellent idea :) my only improvement might be to use Popen3 so you can better interact with the sub-processes [1], but if you didn't need to in your case, no worries!
-- Lee Hambley Twitter: @leehambley Blog: http://lee.hambley.name/ Working with Rails: http://is.gd/1s5W1 --- [1] http://tech.natemurray.com/2007/03/ruby-shell-commands.html 2009/8/25 Donovan Bray <[email protected]> > > I've solved a similar problem by using system() and passing the whole > cap task back to the system. > > task :default do > system "cap deploy:kon" > system "cap deploy:api" > end > > I did this because the task deploy chains were incompatable with each > other but still wanted to have a single task to run both. > > > On Aug 21, 2009, at 9:03 AM, Rory McKinley > <[email protected]> wrote: > > > > > Hi All > > > > I have a deploy namespace that has two tasks that deploy from > > different > > repositories to different release paths and they use different roles. > > > > The two tasks being called as follows: > > > > cap development deploy:kon > > cap development deploy:api > > > > I would like to combine these two subtasks in a third task (so I rn > > them > > both with a single call), while still retaining the ability to call > > them > > individually. So, I create a task that looks roughly like this: > > > > task :default do > > api > > kon > > end > > > > The problem is that when kon runs it uses the current_path and > > repository defined by api - is there anyway to reset these two > > variables > > to the kon-specific values at the start of the kon tasks? > > > > Regards > > > > Rory > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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.co.uk/group/capistrano?hl=en -~----------~----~----~----~------~----~------~--~---
