-
Bug
-
Resolution: Duplicate
-
Major
-
Jenkins version 2.138.3 running on Linux
When upgrading to version 2.29 of the "Pipeline: Job" plugin, users had a completely empty console output in case of an error.
Downgrading to version 2.28 fixed the issue.
When investigating we found an error log that a log file could not be located:
java.io.FileNotFoundException: /var/lib/jenkins/jobs/iText-merge-pipeline/builds/319/log (No such file or directory)
See attachments for screenshots of the console output and the log.
If I read the change log for version 2.29
- JENKINS-54128: Change the implementation of WorkflowRun#getLogFile to avoid creating a new temporary file each time the method is called.
- Fix: Do not call WorkflowRun#getLogFile when an error occurs while opening the log file for a Pipeline to avoid logging an additional stack trace
My guess would be that WorkflowRun#getLogFile is also not called when an error is thrown in a pipeline script.
- duplicates
-
JENKINS-54678 Compression trick not supported by JEP-210
-
- Open
-
[JENKINS-55024] Pipeline Job Plugin (workflow-job-plugin) gives empty console output when an error occurs
Labels | Original: pipeline plugin | New: pipeline pipeline-triaged plugin |
Resolution | New: Incomplete [ 4 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Attachment | New: test-pipeline-Jenkinsfile [ 47403 ] |
Resolution | Original: Incomplete [ 4 ] | |
Status | Original: Resolved [ 5 ] | New: In Review [ 10005 ] |
Attachment | New: consoleText-iTextMergePipeline.txt.xz [ 47463 ] |
Status | Original: In Review [ 10005 ] | New: In Progress [ 3 ] |
Status | Original: In Progress [ 3 ] | New: Open [ 1 ] |
Labels | Original: pipeline pipeline-triaged plugin | New: pipeline pipeline-triaged |
Attachment | New: image-2019-06-05-14-55-49-292.png [ 47593 ] |
Attachment | New: image-2019-06-05-14-56-21-611.png [ 47594 ] |