Background:
On deploy we create a lockfile to ensure no one can deploy while
another deploy is going out. At the end of the code update, the
lockfile is removed. Unfortunately, if an exception is raised before
the remove lock file task is run, the file stays there. (We can
remove it manually, but that is annoying)
Question:
I couldn't find in the docs, is there some kind of hook for handling
shutdown
trap("INT") { deploy.shutdown }
namespace :deploy do
task :shutdown {}
end
so that I can
after 'deploy:shutdown', 'deploy:unlock'
or is there a place I could put an 'ensure' block?
note: specifically we are using this recipe
https://github.com/ndbroadbent/capistrano_deploy_lock
Thanks
-Benjamin
--
--
* 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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
