[JIRA] (JENKINS-52661) P4 Plugin fails to parse changelog
Title: Message Title
Noel C edited a comment on JENKINS-52661
Re: P4 Plugin fails to parse changelog
Hi,I am getting similar issue where Jenkins is not able to generate the changes (e.g. "No changes from last build"). But changelog.xml exist and looks valid. It looks like my issue is due to special characters (e.g. "&", and "+" at least) within the tags such as below{color:#b00117}blahblah_&_blahblah clientI clientId> {color}I see the below in my Jenkins log:Could not parse Perforce changelog: /var/lib/jenkins/jobs//builds/28/changelog.xml{color:#88aa88}Aug 01, 2019 8:54:08 AM{color} {color:#aa}SEVERE{color} {color:#aa}org.jenkinsci.plugins.p4.changes.P4ChangeParser parse {color}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192535.1532016996000.5718.1564686360526%40Atlassian.JIRA.
[JIRA] (JENKINS-52661) P4 Plugin fails to parse changelog
Title: Message Title Noel C commented on JENKINS-52661 Re: P4 Plugin fails to parse changelog Hi, I am getting similar issue where Jenkins is not able to generate the changes (e.g. "No changes from last build"). But changelog.xml exist and looks valid. It looks like my issue is due to special characters (e.g. "&", and "+" at least) within the tags such as below blahblah_&_blahblah I see the below in my Jenkins log: Could not parse Perforce changelog: /var/lib/jenkins/jobs//builds/28/changelog.xml Aug 01, 2019 8:54:08 AM SEVERE org.jenkinsci.plugins.p4.changes.P4ChangeParser parse Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192535.1532016996000.5710.1564686300270%40Atlassian.JIRA.
[JIRA] (JENKINS-52661) P4 Plugin fails to parse changelog
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-52661 P4 Plugin fails to parse changelog Change By: Paul Allen Comment: Released in 1.9.5A '?' character is used for any low ascii characters not supported by XML. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52661) P4 Plugin fails to parse changelog
Title: Message Title Paul Allen updated JENKINS-52661 Released in 1.9.5 A '?' character is used for any low ascii characters not supported by XML. Jenkins / JENKINS-52661 P4 Plugin fails to parse changelog Change By: Paul Allen Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52661) P4 Plugin fails to parse changelog
Title: Message Title Paul Allen commented on JENKINS-52661 Re: P4 Plugin fails to parse changelog Released in 1.9.5 A '?' character is used for any low ascii characters not supported by XML. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52661) P4 Plugin fails to parse changelog
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-52661 P4 Plugin fails to parse changelog Change By: Paul Allen Labels: P4_A P4_VERIFY SAXParseException Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52661) P4 Plugin fails to parse changelog
Title: Message Title Paul Allen assigned an issue to Paul Allen Jenkins / JENKINS-52661 P4 Plugin fails to parse changelog Change By: Paul Allen Assignee: Paul Allen Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52661) P4 Plugin fails to parse changelog
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-52661 P4 Plugin fails to parse changelog Change By: Paul Allen Labels: P4_A P4_VERIFY SAXParseException Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52661) P4 Plugin fails to parse changelog
Title: Message Title Paul Allen started work on JENKINS-52661 Change By: Paul Allen Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52661) P4 Plugin fails to parse changelog
Title: Message Title Paul Allen updated JENKINS-52661 Ready for release. Jenkins / JENKINS-52661 P4 Plugin fails to parse changelog Change By: Paul Allen Status: In Progress Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52661) P4 Plugin fails to parse changelog
Title: Message Title Karl Wirth commented on JENKINS-52661 Re: P4 Plugin fails to parse changelog Have worked with Peter and reproduced the XML parse error he reported. Created new defect: JENKINS-54841 We believe the original problem still exists and is related to multiple nodes running at the same time potentially causing concurrency issues reading and writing the changelog.xml. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52661) P4 Plugin fails to parse changelog
Title: Message Title peter anderson updated an issue Jenkins / JENKINS-52661 P4 Plugin fails to parse changelog Change By: peter anderson Attachment: changelog2.xml Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52661) P4 Plugin fails to parse changelog
Title: Message Title peter anderson updated an issue Jenkins / JENKINS-52661 P4 Plugin fails to parse changelog Change By: peter anderson Attachment: changelog2.xml Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52661) P4 Plugin fails to parse changelog
Title: Message Title peter anderson edited a comment on JENKINS-52661 Re: P4 Plugin fails to parse changelog I have added another case where the xml parser fails. This time it appears to be related to the perforce commit comment containing a unicode character: !screenshot-1.png|thumbnail! These kinds of errors cause the job to fail in jenkins - this is a big problem considering some builds trigger of the success of another build. They shouldn't be failing for this reason. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52661) P4 Plugin fails to parse changelog
Title: Message Title peter anderson updated an issue Jenkins / JENKINS-52661 P4 Plugin fails to parse changelog Change By: peter anderson Attachment: screenshot-1.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52661) P4 Plugin fails to parse changelog
Title: Message Title peter anderson commented on JENKINS-52661 Re: P4 Plugin fails to parse changelog I have added another case where the xml parser fails. This time it appears to be related to the perforce commit comment containing a unicode character: Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52661) P4 Plugin fails to parse changelog
Title: Message Title
peter anderson updated an issue
Jenkins / JENKINS-52661
P4 Plugin fails to parse changelog
Change By:
peter anderson
Some Jenkins jobs fail because the P4 plugin is not able to parse the changelog: {noformat}org.xml.sax.SAXParseException; systemId: file:/var/jenkins_home/jobs/Maintenance/builds/4/changelog5.xml; lineNumber: 1; columnNumber: 1; Premature end of file. at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:203) at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:177) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:400) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:327) at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1472) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:1014) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:602) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:505) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:841) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:770) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1213) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:643) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(SAXParserImpl.java:327) at javax.xml.parsers.SAXParser.parse(SAXParser.java:328) at org.jenkinsci.plugins.p4.changes.P4ChangeParser.parse(P4ChangeParser.java:50) Caused: org.xml.sax.SAXException: Could not parse perforce changelog: org.xml.sax.SAXParseException; systemId: file:/var/jenkins_home/jobs/Maintenance/builds/4/changelog5.xml; lineNumber: 1; columnNumber: 1; Premature end of file. at org.jenkinsci.plugins.p4.changes.P4ChangeParser.parse(P4ChangeParser.java:54) at org.jenkinsci.plugins.workflow.job.WorkflowRun.onCheckout(WorkflowRun.java:847) at org.jenkinsci.plugins.workflow.job.WorkflowRun.access$1500(WorkflowRun.java:143) at org.jenkinsci.plugins.workflow.job.WorkflowRun$SCMListenerImpl.onCheckout(WorkflowRun.java:1041) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:127) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:85) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:75) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at hudson.security.ACL.impersonate(ACL.java:290) at
[JIRA] (JENKINS-52661) P4 Plugin fails to parse changelog
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-52661 P4 Plugin fails to parse changelog Change By: Paul Allen Labels: P4_VERIFY SAXParseException changelog p4changeeparser Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52661) P4 Plugin fails to parse changelog
Title: Message Title Eric Lloyd commented on JENKINS-52661 Re: P4 Plugin fails to parse changelog I was also seeing this issue when running many parallel stages all doing checkouts. It seems like some of the stages start before the changlog.xml is fully generated. After the build finishes if I go on the master and check the changelog is correct. To fix this, for now, I had to move to only allow one stage to checkout at a time but that is less than Ideal. I am using P4 plugin version 1.8.14 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52661) P4 Plugin fails to parse changelog
Title: Message Title
Robert Pitt edited a comment on JENKINS-52661
Re: P4 Plugin fails to parse changelog
Note we're still suffering from this in a number of jobs.Some additional context, the file in question invariably looks perfectly but with 0 changes (valid/expected) :{noformat}{noformat}We're using it in a pipeline job which does multiple checkouts (we have multiple p4 servers).I'm not sure we've ever seen it in a job which does a single checkout from one server.
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52661) P4 Plugin fails to parse changelog
Title: Message Title Robert Pitt commented on JENKINS-52661 Re: P4 Plugin fails to parse changelog Note we're still suffering from this in a number of jobs. Some additional context, the file in question invariably looks perfectly but with 0 changes: We're using it in a pipeline job which does multiple checkouts (we have multiple p4 servers). I'm not sure we've ever seen it in a job which does a single checkout from one server. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
