[JIRA] (JENKINS-39337) error step has no log output
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-39337 error step has no log output Issue Type: Bug Assignee: Unassigned Components: workflow-basic-steps-plugin Created: 2016/Oct/28 1:10 AM Priority: Minor Reporter: Michael Neale if you use "error 'help'" in a pipeline, the pipeline will exit. The text 'help' appears in the overall log, but not in the log for the step/node. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39337) error step has no log output
Title: Message Title Jesse Glick resolved as Not A Defect As designed. It throws up an exception. Whoever catches that exception may choose to log it, or not. If the exception terminates the build, the build log shows it. ErrorAction can be used to determine which steps terminated with this exception. Jenkins / JENKINS-39337 error step has no log output Change By: Jesse Glick Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To u
[JIRA] (JENKINS-39337) error step has no log output
Title: Message Title
Michael Neale commented on JENKINS-39337
Re: error step has no log output
How is this designed at all? if it just throws an exception, why does this step exist? it doesn't provide anything extra over throw Exception("message here")? It should at least log the message, or else be removed as a step with no purpose.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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-39337) error step has no log output
Title: Message Title Michael Neale reopened an issue Jenkins / JENKINS-39337 error step has no log output Change By: Michael Neale Resolution: Not A Defect Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-39337) error step has no log output
Title: Message Title
Jesse Glick resolved as Not A Defect
why does this step exist? it doesn't provide anything extra over throw Exception("message here")?
new hudson.AbortException('message') specifically, which is not whitelisted, and not really something a user would be expected to know about. There is also an open RFE to allow you to set the build status, which would be an even more torturous and non-whitelisted construction if you had to do it by hand.
It should at least log the message
No, it should not. It is up to the catcher to decide whether and how to respond to an exception.
Jenkins / JENKINS-39337
error step has no log output
Change By:
Jesse Glick
Status:
Reopened Resolved
Resolution:
Not A Defect
Add Comment
This message was sent by Atlassian JIRA (v
