Details
-
Type:
Improvement
-
Status: In Progress (View Workflow)
-
Priority:
Major
-
Resolution: Unresolved
-
Component/s: workflow-basic-steps-plugin
-
Labels:
-
Similar Issues:
-
Epic Link:
Description
When a flow involves many steps, long logs, and/or many branches, it can be hard for a developer receiving a failure email (for example) to quickly see what part of the build actually failed and why. I think it would be useful for the catchError step to do a DFS search on the Throwable and its cause chain through the FlowNode graph starting at the end of the catch step, looking for ErrorAction, and setting/appending an environment variable with the URL of the LogAction. Or provide a new step to do the same. Thus you could write
def runStuff(param) {
...
}
try {
parallel a: {runStuff 'a'}, b: {runStuff 'b'}
} catch (e) {
mail to: '...', subject: 'Failure!', body: "Build failed: ${errorUrl(e)}"
}
and get a link to http://jenkins/job/myflow/123/flowGraph/77/console or the like, according to the actual step in one of the branches that threw the error.
Attachments
Issue Links
- depends on
-
-
- Open
-
- is duplicated by
-
JENKINS-38156 Need branch name and other details from parallel branches
-
- Resolved
-
- is related to
-
JENKINS-25894 Ugly reporting of errors from parallel step
-
- Resolved
-
-
JENKINS-26107 Allow stage to operate as a labelled block
-
- Closed
-
- relates to
-
-
- Resolved
-
- links to
Activity
Is there already any way to get the link to 'blue/rest/organizations/jenkins/pipelines/<jobname>/runs/<build-id>/nodes/<PipelineNodeImpl-id>/log/ from within a pipeline parallel node?
Gonna be harsh here, but rightfully so. I feel burned, I worked many days to set up docker containers, scripts and even fixing and compiling plugins, and I now find out that it's for naught.
"run a command and produce a URL to the output" is basic functionality of a CI tool.
There's no point in using Jenkins without it (for me).
Erik van Velzen
added a comment - - edited Gonna be harsh here, but rightfully so. I feel burned, I worked many days to set up docker containers, scripts and even fixing and compiling plugins, and I now find out that it's for naught.
"run a command and produce a URL to the output" is basic functionality of a CI tool.
There's no point in using Jenkins without it (for me). Perhaps a workaround would be to pipe the output within the step to a file and publish it as an artifact.
Erik van Velzen
added a comment - Perhaps a workaround would be to pipe the output within the step to a file and publish it as an artifact. Erik van Velzen if you are using blue ocean, you can just have the link to the build and once the page open it will automatically scroll to the failed step.
also another work around https://stackoverflow.com/questions/53444196/get-log-for-each-jenkins-pipeline-stage
thang bui
added a comment - - edited Erik van Velzen if you are using blue ocean, you can just have the link to the build and once the page open it will automatically scroll to the failed step.
also another work around https://stackoverflow.com/questions/53444196/get-log-for-each-jenkins-pipeline-stage
just up-voted;
Me too, I have similar usecase. In our testenvironment, we run many tools, each generating a separate logfile. We have one generic log shown in the console.
If one test fails, we can see that it failed, and typically have an exception message shown in the console, but the actual (detailed) reason is hidden in one of
the detailed logs. For that reason we want to include a link to the workspace directory on the exception text, such that all the log-files are just one click away.
For the pipeline jobs that link is not easy to derive; it is hidden in one of the pipeline steps. as also indicated by Craig Ringer
My feeling says that making sure that link, or the ID is available at runtime should be possible ... right ?