-
Bug
-
Resolution: Unresolved
-
Major
-
None
If you attempt to install a tool that doesn't exist, the step will fail, but there is nothing in the steps log.
You would see something like the attached in the stage view. The log should explain what is missing in the tool:
(problem isn't with stage view, but is with the steps output)
To reproduce:
node {
stage 'Checkout'
checkout scm
stage 'Build'
def mvnHome = tool 'NONSENSE'
}
and look at the stage graph to see that it has no output
[JENKINS-38776] tool step does not report failures in its log
| Rank | New: Ranked higher |
| Link |
New:
This issue duplicates |
| Link |
Original:
This issue duplicates |
| Priority | Original: Minor [ 4 ] | New: Major [ 3 ] |
Hrm perhaps this should be broadened to capture all failure logs where possible (the trick is each step has its own impl...)
| Assignee | Original: rsandell [ rsandell ] |
| Attachment | New: screenshot-1.png [ 40162 ] |
michaelneale abayer Looks like this bug is specific to stage view plugin. Blueocean shows the error correctly:
This issue isn't just related to a missing tool. Any command that fails doesn't have its return code or any other failure reported in the log for that step/stage. This is particularly frustrating when the timeout plugin or "parallel.failFast = true" feature of a Jenkinsfile terminates the build, but you can't tell why.