Hook that task to: after "deploy:restart"
If a deploy rolls back due to a problem the restart will never get hit; thus only notifying you of a good deploy. Also you can include any evironment variable like say: ENV['USER'] in that message so you know who to blam... Err congratulate. On Aug 2, 2011, at 8:53 AM, Prof Falken <[email protected]> wrote: > Hi all, > > I'm writing a recipe for Cap which should enable us to publish notifications > of cap deploys via XMPP. > > The message I want to send is something along the lines of: > > "#{local_user_name} published version #{release} of #{application} to > #{stage} - result was: #{cap_deploy_result}" > > I've got the "release", "application" and "stage" variables working from > other things, however I'd love to know if it's possible to retrieve the > status of the cap run (this task is designed to run after a deploy) and the > local user (i.e. the person who is running the deploy). > > I've found a couple of sites which mention all the config vars you can use, > but I'm struggling to find anything which lists the available variables for > use in your own recipes. > > If it requires a patch etc, let me know and I'll update my fork on github. > > Cheers, > > Matt > -- > * 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.com/group/capistrano?hl=en -- * 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.com/group/capistrano?hl=en
