Hi Lee, All we need at work is XMPP support, although for a few things I'm playing around with outside $dayjob, different notification types would be useful.
I'm going to try and write an extensible framework for notifications - I'll let you know once I've got some ideas/code to try... :) Cheers M. On 2 August 2011 18:04, Lee Hambley <[email protected]> wrote: > Matt, as far as I know there's nothing like "cap deploy result" - you can > assume if you are in an after-callback that it was successful, otherwise the > transaction would have been aborted earlier in the process. > As for "local username" - there's some options here, shell-out, to "whoami", > if all your users are on *NIX, or if you want to make something a bit more > portable, you can use the 'etc' library from the std lib: > ruby-1.9.2-p290 :015 > require 'etc' > => false > ruby-1.9.2-p290 :016 > Etc.getlogin > => "codebeaker" > - YMMV on Windows, but I can imagine "etc" is portable (having not touched a > Windows PC in years, I can't speak for or against) > I'd love to have something like a "notify" callback, globally available for > a more full-featured deploy, so I'd love for you to consider packaging this > as an "official" extension sometime; once it's working and useful for you > and your team, of course. > On 2 August 2011 17:53, 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 -- * 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
