Title: Message Title
John Elion created an issue
Jenkins / JENKINS-40633
Log parser should emit string in log indicating it found a problem.
Issue Type:
Improvement
Assignee:
Manuel Recena Soto
Components:
log-parser-plugin
Created:
2016/Dec/22 1:16 PM
Environment:
Jenkins 2.19.4, log-parser 2.0
Priority:
Minor
Reporter:
John Elion
I suggest that the console log parser ought to emit a message in the build log when it finds one or more errors that fails the build. I concede that I am guessing: I had what appeared to be a successful build, except that the build failure analyzer detected "Build step 'Use publishers from another project' changed build result to FAILURE". However, none of the publisher build steps showed any signs of failure. After some study, It dawned on me to check the parsed console log where I discovered a single error had been reported that had no other consequences (i.e., despite the error Ant reported BUILD SUCCESSFUL and a usable artifact was produced.) I am guessing that by detecting an error, the console log parser failed the build. It would have been helpful if when it ran, it reported that it had detected an error in the console log and failed the build - I would have got to the parsed console output a lot sooner. Very nice plugin. By writing up these details I in no way mean to imply the utility is bad; rather, I took the time to write this up because I think it is a great tool and this is something that I hope will be easy to implement and when done, it will help more readily guide the user to the source of problems.
