capistrano/spec/support/tasks/fail.rake

set :fail, proc { fail }
before 'deploy:starting', :fail do
  on roles :all do
    execute :mkdir, '-p', shared_path
    execute :touch, shared_path.join('fail')
  end
  fetch(:fail)
end
Add hook for deploy failure If an error is raised during a deploy, the task `deploy:failed` will be triggered. Custom tasks can hook into this using `after`: after 'deploy:failed', :send_for_help do # end I've also taken the opportunity to provide a marginally more useful error message before triggering the task. By default, this 'deploy:failed' will only be triggered when running `cap <stage> deploy` - to trigger after individual tasks use `set :deploying, true` This closes #708 and replaces https://github.com/capistrano/capistrano/pull/720 2013-11-01 11:59:13 +00:00			`set :fail, proc { fail }`
			`before 'deploy:starting', :fail do`
			`on roles :all do`
Fix broken deploy_failure.feature tests It seems that enhancing a task using an `after` block will not have desired effect if the new task shares the same name (excluding namespace) as the task being enhanced. In other words, `after 'deploy:failed', :failed do ...` will not work (the block will never be executed). This behavior was recently introduced in 5fcf3da. To fix the feature test using this code, I renamed the task to be a unique name. The test now works as intended. Also, I noticed the task defined in `fail.rake` was sometimes not working as intended, because the `shared_path` did not exist on the VM's filesystem. This meant that `touch` was failing. Corrected by issuing `mkdir -p` first. With these changes, all feature tests now pass. 2015-12-27 16:49:31 -08:00			`execute :mkdir, '-p', shared_path`
Add hook for deploy failure If an error is raised during a deploy, the task `deploy:failed` will be triggered. Custom tasks can hook into this using `after`: after 'deploy:failed', :send_for_help do # end I've also taken the opportunity to provide a marginally more useful error message before triggering the task. By default, this 'deploy:failed' will only be triggered when running `cap <stage> deploy` - to trigger after individual tasks use `set :deploying, true` This closes #708 and replaces https://github.com/capistrano/capistrano/pull/720 2013-11-01 11:59:13 +00:00			`execute :touch, shared_path.join('fail')`
			`end`
			`fetch(:fail)`
			`end`