[JIRA] (JENKINS-44930) Allow sh to return exit status, stdout and stderr all at once
Title: Message Title ilya s commented on JENKINS-44930 Re: Allow sh to return exit status, stdout and stderr all at once Here's my use case for this: aws ecr describe-repositories --repository-names foo I want to check if a Docker repository exists. On success, this command returns a JSON blob in stdout. On failure, it returns a string into stderr. As of right now, what should be a simple case of pattern-matching on the stderr content when exit code != 0 turns into something completely different. I've not yet came to a solution, but it's disappointing that what looks like shell invocation step behaves nothing like the shell in practice. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183003.149756330.2426.1578268383396%40Atlassian.JIRA.
[JIRA] (JENKINS-40839) pipeline timeout doesn't kill the job
Title: Message Title ilya s edited a comment on JENKINS-40839 Re: pipeline timeout doesn't kill the job Doesn't that basically defeat the purpose of this step? The expectation for users is that the timeout will kill whatever's in the timeout block. Effectively, this means that timeouts cannot be enforced by the pipeline when using libraries that aren don 't explicitly rethrow timeout exceptions. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40839) pipeline timeout doesn't kill the job
Title: Message Title ilya s commented on JENKINS-40839 Re: pipeline timeout doesn't kill the job Doesn't that basically defeat the purpose of this step? The expectation for users is that the timeout will kill whatever's in the timeout block. Effectively, this means that timeouts cannot be enforced by the pipeline when using libraries that aren't explicitly rethrow timeout exceptions. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40839) pipeline timeout doesn't kill the job
Title: Message Title ilya s commented on JENKINS-40839 Re: pipeline timeout doesn't kill the job According to this example that's not accurate, since in the output we still get the second echo from within the timeout block. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
