-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
centos 7
ERROR: [withMaven] WARNING Exception parsing the logs generated by the Jenkins Maven Event Spy /var/lib/jenkins/workspace/REDACTED_master@tmp/withMaven90609b9c/maven-spy-20191107-123951-371640815890573653522.log, ignore file. Please report a bug associated for the component 'pipeline-maven-plugin' at [https://issues.jenkins-ci.org|https://issues.jenkins-ci.org/] ERROR: org.xml.sax.SAXParseException; lineNumber: 2267; columnNumber: 39; An invalid XML character (Unicode: 0x1b) was found in the element content of the document.
- is related to
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
[JENKINS-60093] WARNING Exception parsing the Jenkins Maven Event Spy logs due to An invalid XML character
Jason Pyeron
added a comment - the log file is gone, the "tmp" workspace is empty of all files. According to https://unicodelookup.com/#0x1b/1 , `#0x1b` is `esc escape ctrl-[`
Jason Pyeron
added a comment - but why was it there.... My guess is Maven color codes, along with broken build, ... We continue to monitor, but we do not have any retained logs at this moment.
Jason Pyeron
added a comment - but why was it there.... My guess is Maven color codes, along with broken build, ... We continue to monitor, but we do not have any retained logs at this moment. jpyeron Not sure if you saw this already in the docs on https://plugins.jenkins.io/pipeline-maven, but if you touch a file named .archive-jenkins-maven-event-spy-logs inside of the workspace used by withMaven, the XML file will be archived going forward, so when a problem happens you'll have the XML file on hand.
jpyeron as dnusbaum has said, can you please collect the log file using the FAQ entry "How do I capture the log file generated by the Jenkins Maven Event Spy" https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin#PipelineMavenPlugin-HowdoIcapturethelogfilegeneratedbytheJenkinsMavenEventSpy
The build script will look like
withMaven() {
sh "mvn verify"
writeFile file: '.archive-jenkins-maven-event-spy-logs', text: ''
} // will discover the marker file ".archive-jenkins-maven-event-spy-log" and will archive the maven event spy log file maven-spy-....log
A log file with the output of the "Jenkins Maven Event Spy"" will be added to the archived artifacts of your build. It will look like:
Jason Pyeron
added a comment - got it, but we have not yet reproduced the condition where the ESC char was emitted.
Jason Pyeron
added a comment - got it, but we have not yet reproduced the condition where the ESC char was emitted. jpyeron do you mean that your problem disappeared and that your pipeline is back executing as expected?
Can you try to find in the generated log file what's located at `lineNumber: 2267; columnNumber: 39` ?
not sure if it a proper duplicate, but these seem similar.