-
Notifications
You must be signed in to change notification settings - Fork 2
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
Document behaviour of SSH functionality #9
Comments
@Jelle-S something for monday? :) |
https://github.com/digipolisgent/robo-digipolis-deploy/blob/bf749564bd83e99e09fc038b5f783a29726c43f6/src/Ssh.php#L285 shows that when stoponfail is true, the result is an error, however. when stoponfail is false and there is an error message, stoponfail isn't taken into account. |
Ok, so should we change this behavior? Meaning that if What Robo themselves do is pretty weird too tho, see https://github.com/consolidation/Robo/blob/b027871e12c7433457fb326be64fc81198d03f51/src/Task/CommandStack.php Looking at the code, when The for the ssh tasks defined by Robo (https://github.com/consolidation/Robo/blob/047af4b4465e5381d5ee691a7ee8194ede890c9c/src/Task/Remote/Ssh.php#L210) the behavior is different too. Based on I personally think the behavior is the Robo Any thoughts @daften? |
Mainly how it differs from SSH functionality in robo core and why (stopOnFail flag and concatenation of commands)
The text was updated successfully, but these errors were encountered: