Fixed exitcodes - #37
Merged
Merged
Conversation
…the application so the correct exit code will be generated.
Member
|
Thanks, merged it and released v1.3.0. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I've adjusted the code of the patch classes so exceptions which are generated there are not catched in the same class as well. This way the exceptions bubble up to the Application which can respond more appropriate.
As a result exceptions in the patch itself will cause an exitcode of 1, which I think is more correct. I my specific case deployments using Capistrano will now fail if a DB patch fails.