[JIRA] (JENKINS-60093) WARNING Exception parsing the Jenkins Maven Event Spy logs due to An invalid XML character

[jpyeron@pdinc.us (JIRA)]

Jason Pyeron commented on JENKINS-60093

Re: WARNING Exception parsing the Jenkins Maven Event Spy logs due to An invalid XML character not sure if it a proper duplicate, but these seem similar. Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

[jpyeron@pdinc.us (JIRA)]

Jason Pyeron updated an issue

Jenkins / JENKINS-60093

WARNING Exception parsing the Jenkins Maven Event Spy logs due to An invalid XML character

Change By: Jason Pyeron {noformat} 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 |mailto:/var/lib/jenkins/workspace/proval-devint-deploy-war2_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. {noformat}

Add Comment

[jpyeron@pdinc.us (JIRA)]

Jason Pyeron commented on JENKINS-60093

Re: WARNING Exception parsing the Jenkins Maven Event Spy logs due to An invalid XML character the log file is gone, the "tmp" workspace is empty of all files.

Add Comment

[jpyeron@pdinc.us (JIRA)]

Jason Pyeron created an issue

Jenkins / JENKINS-60093

WARNING Exception parsing the Jenkins Maven Event Spy logs due to An invalid XML character

Issue Type: Bug Assignee: Alvaro Lobato Components: pipeline-maven-plugin Created: 2019-11-07 17:49 Environment: centos 7 Priority: Minor Reporter: Jason Pyeron 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|mailto:/var/lib/jenkins/workspace/proval-devint-deploy-war2_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.

Add Comment

[cleclerc@cloudbees.com (JIRA)]

Cyrille Le Clerc commented on JENKINS-60093

Re: WARNING Exception parsing the Jenkins Maven Event Spy logs due to An invalid XML character According to https://unicodelookup.com/#0x1b/1 , `#0x1b` is `esc escape ctrl-[`

Add Comment

[jpyeron@pdinc.us (JIRA)]

Jason Pyeron commented on JENKINS-60093

Re: WARNING Exception parsing the Jenkins Maven Event Spy logs due to An invalid XML character

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.

Add Comment

[dnusbaum@cloudbees.com (JIRA)]

Devin Nusbaum commented on JENKINS-60093

Re: WARNING Exception parsing the Jenkins Maven Event Spy logs due to An invalid XML character

Jason Pyeron 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.

Add Comment

[cleclerc@cloudbees.com (JIRA)]

Cyrille Le Clerc commented on JENKINS-60093

Re: WARNING Exception parsing the Jenkins Maven Event Spy logs due to An invalid XML character

Jason Pyeron as Devin Nusbaum 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:

Add Comment

[cleclerc@cloudbees.com (JIRA)]

Cyrille Le Clerc updated an issue

Jenkins / JENKINS-60093

WARNING Exception parsing the Jenkins Maven Event Spy logs due to An invalid XML character

Change By: Cyrille Le Clerc Attachment: image-2019-11-14-14-45-10-102.png

Add Comment

[jpyeron@pdinc.us (JIRA)]

Jason Pyeron commented on JENKINS-60093

Re: WARNING Exception parsing the Jenkins Maven Event Spy logs due to An invalid XML character got it, but we have not yet reproduced the condition where the ESC char was emitted.

Add Comment

[cleclerc@cloudbees.com (JIRA)]

Cyrille Le Clerc commented on JENKINS-60093

Re: WARNING Exception parsing the Jenkins Maven Event Spy logs due to An invalid XML character

Jason Pyeron 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` ?

Add Comment