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.