I'm attempting to determine which deployment tasks will accept and use git commit SHA1s (i can get them into cap via either -S branch=<SHA1> or with CLI). I'm deploying 2 separate git repositories, to multiple stages and I'd like the ability to specify the SHA1 for each deployment operation (if it makes sense and is possible). I've been reading through the cap codebase (mostly at deploy.rb and git.rb) but I'm having a hard time following the execution paths of each of these commands. Looking at this list, can anyone tell me which of these make sense to use a commit SHA1 and what the effect would be? The ones I'm concerned with are:
deploy:pending, deploy:pending:diff, deploy:rollback, deploy:rollback:code, deploy:update, deploy:update_code shell If you're a cap expert anywhere near me in LA (hollywood) I'll buy you some beers for your help! :) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
