Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add deploy failure handling to cap v2 and v3. #135

Merged
merged 1 commit into from
Apr 3, 2018

Conversation

phillbaker
Copy link
Contributor

This handles the case where any of the steps in the deploy process after quieting sidekiq fail, e.g. pulling from git, compiling assets, etc.

For cap v2, this is documented here: https://github.com/leehambley/capistrano-handbook/blob/master/index.markdown#transactions

For cap v3, the pull request adding support is here: capistrano/capistrano#756.

I think this was the intention of #105.

This handles the case where any of the steps in the deploy process after quieting sidekiq fail, e.g. pulling from git, compiling assets, etc.

For cap v2, this is documented here: https://github.com/leehambley/capistrano-handbook/blob/master/index.markdown#transactions

For cap v3, the pull request adding support is here: capistrano/capistrano#756.

I think this was the intention of seuros#105.
@phillbaker
Copy link
Contributor Author

Bump @seuros, any thoughts on this?

@alto
Copy link

alto commented Oct 26, 2016

+1

1 similar comment
@MichaelKuhinica
Copy link

👍

@seuros seuros merged commit 1152d41 into seuros:master Apr 3, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants