• Type: Bug
• Resolution: Fixed
• Priority: Major
• Component/s: pipeline-maven-plugin
• Labels:

  None
• Environment:

  Java 8
  Maven 3.3
  Jenkins 2.51
  Pipeline 2.5
  Pipeline Maven Integration Plugin 2.0

1. event spy log sanitized

   24 kB

   2017-03-28 12:24

[JENKINS-43159] maven-spy log contains invalid XML

Ollie Robertshaw created issue - 2017-03-28 12:23

Ollie Robertshaw made changes - 2017-03-28 12:23

Summary

Original: Invalid maven-spy log generated

New: Generated invalid XML in maven-spy log

Ollie Robertshaw made changes - 2017-03-28 12:24

Attachment

New: event spy log sanitized [ 36801 ]

Ollie Robertshaw made changes - 2017-03-28 12:25

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}

Ollie Robertshaw made changes - 2017-03-28 12:27

Summary

Original: Generated invalid XML in maven-spy log

New: maven-spy log contains invalid XML

Ollie Robertshaw made changes - 2017-03-28 12:28

Priority

Original: Minor [ 4 ]

New: Major [ 3 ]

Cyrille Le Clerc made changes - 2017-04-08 16:09

Assignee

Original: Alvaro Lobato [ alobato ]

New: Cyrille Le Clerc [ cleclerc ]

Cyrille Le Clerc made changes - 2017-04-08 16:17

Link

New: This issue is blocked by JENKINS-43449 [ JENKINS-43449 ]

Cyrille Le Clerc made changes - 2017-04-09 19:10

Status

Original: Open [ 1 ]

New: In Progress [ 3 ]

Cyrille Le Clerc made changes - 2017-04-11 07:47

Status

Original: In Progress [ 3 ]

New: In Review [ 10005 ]

Cyrille Le Clerc made changes - 2017-04-11 07:48

Resolution		New: Fixed [ 1 ]
Status	Original: In Review [ 10005 ]	New: Resolved [ 5 ]

Load more newer history items