-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Java 8
Maven 3.3
Jenkins 2.51
Pipeline 2.5
Pipeline Maven Integration Plugin 2.0
Our maven-spy-*.log file is being generated with broken XML, for example:
... <ExecutionEvent type="> <ExecutionEventProjectStarted" class=" type="org.apache.maven.lifecycle.internal.DefaultExecutionEvent" _time="ProjectStarted"2017-03-28 12:05:43.464"> ...
This happens with other elements too; in this particular case, re-running the job leads to exactly the same malformed XML.
This ultimately leads to an error:
ERROR: [withMaven] WARNING Exception parsing the logs generated by the Jenkins Maven Event Spy /media/ephemeral0/jenkins/workspace/iMain-Pipeline_release_1.44-HEHP3JF3JUC3QDIC42A5YMRMVQTJR3HJ4P7IFHLSMEGVJNWC55SA@tmp/withMaven21be2166/maven-spy-20170328-094339-928.log, ignore file. Please report a bug associated for the component 'pipeline-maven-plugin' at https://issues.jenkins-ci.org ERROR: org.xml.sax.SAXParseException; lineNumber: 246; columnNumber: 16; Element type "ExecutionEvent" must be followed by either attribute specifications, ">" or "/>".
- is blocked by
-
JENKINS-43449 Ensure that the maven-events-spy is thread safe
-
- Closed
-
- is related to
-
JENKINS-60093 WARNING Exception parsing the Jenkins Maven Event Spy logs due to An invalid XML character
-
- Open
-
[JENKINS-43159] maven-spy log contains invalid XML
Summary | Original: Invalid maven-spy log generated | New: Generated invalid XML in maven-spy log |
Attachment | New: event spy log sanitized [ 36801 ] |
Description |
Original:
Our maven-spy-*.log file is being generated with broken XML, for example: {code:java} ... <ExecutionEvent type="> <ExecutionEventProjectStarted" class=" type="org.apache.maven.lifecycle.internal.DefaultExecutionEvent" _time="ProjectStarted"2017-03-28 12:05:43.464"> ...{code} This happens with other elements too; in this particular case, re-running the job leads to exactly the same malformed XML. This ultimately leads to an error: {code:java} ERROR: [withMaven] WARNING Exception parsing the logs generated by the Jenkins Maven Event Spy /media/ephemeral0/jenkins/workspace/iMain-Pipeline_release_1.44-HEHP3JF3JUC3QDIC42A5YMRMVQTJR3HJ4P7IFHLSMEGVJNWC55SA@tmp/withMaven21be2166/maven-spy-20170328-094339-928.log, ignore file. Please report a bug associated for the component 'pipeline-maven-plugin' at https://issues.jenkins-ci.org ERROR: org.xml.sax.SAXParseException; lineNumber: 246; columnNumber: 16; Element type "ExecutionEvent" must be followed by either attribute specifications, ">" or "/>". {code} |
New:
Our maven-spy-*.log file is being generated with broken XML, for example: {code:java} ... <ExecutionEvent type="> <ExecutionEventProjectStarted" class=" type="org.apache.maven.lifecycle.internal.DefaultExecutionEvent" _time="ProjectStarted"2017-03-28 12:05:43.464"> ...{code} This happens with other elements too; in this particular case, re-running the job leads to exactly the same malformed XML. This ultimately leads to an error: {code:java} ERROR: [withMaven] WARNING Exception parsing the logs generated by the Jenkins Maven Event Spy /media/ephemeral0/jenkins/workspace/iMain-Pipeline_release_1.44-HEHP3JF3JUC3QDIC42A5YMRMVQTJR3HJ4P7IFHLSMEGVJNWC55SA@tmp/withMaven21be2166/maven-spy-20170328-094339-928.log, ignore file. Please report a bug associated for the component 'pipeline-maven-plugin' at https://issues.jenkins-ci.org ERROR: org.xml.sax.SAXParseException; lineNumber: 246; columnNumber: 16; Element type "ExecutionEvent" must be followed by either attribute specifications, ">" or "/>". {code} |
Summary | Original: Generated invalid XML in maven-spy log | New: maven-spy log contains invalid XML |
Priority | Original: Minor [ 4 ] | New: Major [ 3 ] |
Assignee | Original: Alvaro Lobato [ alobato ] | New: Cyrille Le Clerc [ cleclerc ] |
Attached log up to the failure. Afterwards would maybe require too much work to sanitize.