Pete, you _could_ use the SCM wrappers...but if you're writing your own tasks, and you know what SCM you are using, there's really no need to. The SCM wrappers only exist so that the deployment strategy code can be SCM agnostic. If you're implementing your own strategy directly, you can just invoke your SCM directly (as I demonstrated in that task in my last email).
You're welcome, of course, to go about this however you choose. You _can_ start with the default deployment tasks and override the ones you need to. It just makes me a little sad when people do that without considering whether they really _need_ to do that. So please tell me you've at least considered the option. :) - Jamis On 1/24/09 7:49 AM, Pete Hodgson wrote: > Lee, thanks for the pointer to the wiki, and more importantly thanks > for taking the time to write the docs you pointed me too! > > Jamis, I see what you're saying re: writing the recipe from scratch. > One thing I'm wondering is whether I can still leverage some of the > utility stuff that capistrano has in it if I do that. The stuff I'm > talking about is things like the wrappers around the scm commands > which I believe exist inside cap somewhere. I'd also like to be able > to use the multistage extension, but I suspect that will be possible > when writing the recipe from scratch. > > Anyway, I shall spelunk around the code a bit (as Lee's 'Capistrano > Execution Path' pdf suggests) and see what I turn up. Thanks again for > the help guys, appreciate it! > > Cheers, > Pete > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
