[JIRA] (JENKINS-57173) Issue with Darcs SCM plugin saving build records
Title: Message Title Sven Strittmatter commented on JENKINS-57173 Re: Issue with Darcs SCM plugin saving build records I incorporated your fixes into the master https://github.com/Weltraumschaf/darcs-plugin. You can try to build the plugin from my sources and test it. I try to figure out how to release and deploy it. It's so long ago, I have no clue how to do it For the Maven build to work you need a Mirror in your settings.xml: repo.jenkins-ci.org m.g.o-public http://repo.jenkins-ci.org/public/ 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.198924.1556132083000.16472.1559197980322%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57173) Issue with Darcs SCM plugin saving build records
Title: Message Title Sven Strittmatter commented on JENKINS-57173 Re: Issue with Darcs SCM plugin saving build records In principle the patches looks good. Is it by accident that there are no commit messages? What I understand: invalid-xml-char.patch and serialization.patch are the required solutions to solve your issues. modernization.patch is not that essential. So plan is: Branch 3.3.x version and incorporate invalid-xml-char.patch and serialization.patch into it and try to release a 3.3.12 of the plugin. The modernization is a not appropriate for a patchlevel release. AFAICS it is at least a minor maybe a mojor. There is also the chance of breaking changes. Also there is an old branch 4.0.0 in which I started to clean up things, add more documentation and write more tests. So my plan is to resurect the 4.0.0 branch and incorporate the modernization patch there and got to 1.0.0. Because I do not plan to add new features. But I won't to fullfil the plugin compatibility test, so that the few users of this plugin can use it safe in the future. But I beg for patience! I have the find out all the rhings I did years ago and why in this plugin and it is not that clean coded as I would expect it nowadays from me 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.198924.1556132083000.8307.1558510920434%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57173) Issue with Darcs SCM plugin saving build records
Title: Message Title Sven Strittmatter commented on JENKINS-57173 Re: Issue with Darcs SCM plugin saving build records I'm not shure how the process is nowadays. As mentioned: It's really long time ago that I made this plugin Patch files are a god way: I'll look inside them at the weekend. And then I figure out how to release and deploy a fixed version. Also I tried to make the plugin compatibility test work, but it looks like that this is a major issue. This darcs plugin is really outdated. 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.198924.1556132083000.2882.1557993420333%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57173) Issue with Darcs SCM plugin saving build records
Title: Message Title Sven Strittmatter commented on JENKINS-57173 Re: Issue with Darcs SCM plugin saving build records I think we have two issues here: A bad character in the log output. A regression due to JEP-200. Why I slurp the whole log I can't tell. I guess I had a reason at the time I developed the plugin. I try to figure out how to fix the JEP-200 issue. The problem that I face is that it is long time ago I did the plugin and worked with Darcs. I do not use Darcs or the plugin since years. So it takes some time for me to understand what I did and why I did it. 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.198924.1556132083000.20651.1557300480105%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57173) Issue with Darcs SCM plugin saving build records
Title: Message Title Sven Strittmatter commented on JENKINS-57173 Re: Issue with Darcs SCM plugin saving build records Did this issue start occuring after upgrading your Jenkins? 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.198924.1556132083000.19779.1557234900154%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57173) Issue with Darcs SCM plugin saving build records
Title: Message Title Sven Strittmatter commented on JENKINS-57173 Re: Issue with Darcs SCM plugin saving build records The used Darcs command is darcs changes --xml-output --summary. 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-57173) Issue with Darcs SCM plugin saving build records
Title: Message Title Sven Strittmatter started work on JENKINS-57173 Change By: Sven Strittmatter 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-57173) Issue with Darcs SCM plugin saving build records
Title: Message Title Sven Strittmatter commented on JENKINS-57173 Re: Issue with Darcs SCM plugin saving build records I digged into it: 0x3 seems to be a control character (ETX) which is not allowed in XML. There is one in the parsed log output. Could you please look into the Darcs XML log output at given line/column mentioned at the bottom of the exception? Maybe darcs is screwing up the log output? I'm not sure if I can handle this malformed XML input in an useful way. 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-57173) Issue with Darcs SCM plugin saving build records
Title: Message Title Sven Strittmatter commented on JENKINS-57173 Re: Issue with Darcs SCM plugin saving build records First I have to admit that I'm really impressed that some still uses this plugin. I'm quite a little bit out of this plugin. I'm also impressed that the plugin still works current Jnkins versions. Anyway... I'll take a look at it in the next days. 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-57173) Issue with Darcs SCM plugin saving build records
Title: Message Title
Sven Strittmatter updated an issue
Jenkins / JENKINS-57173
Issue with Darcs SCM plugin saving build records
Change By:
Sven Strittmatter
When building a job backed on the Darcs SCM plugin, we get this nasty exception. The result is that the build.xml file isn't always saved properly, and we get disappearing builds in the history. {code} Apr 24, 2019 11:43:41 AM org.jenkinsci.plugins.darcs.DarcsChangeLogParser parseINFO: Parsing changelog file /var/lib/jenkins/jobs/Processor Development (PD)/jobs/Typhon/jobs/Tests/jobs/Load Tests/builds/50/changelog.xml...Apr 24, 2019 11:43:41 AM org.jenkinsci.plugins.darcs.DarcsSaxHandler endElementINFO: Ignored tag !Apr 24, 2019 11:43:41 AM jenkins.plugins.slack.logging.SlackNotificationsLogger infoINFO: [Processor Development (PD) » Typhon » Tests » Load Tests #50] found #49 as previous completed, non-aborted buildApr 24, 2019 11:43:41 AM hudson.model.Run executeSEVERE: Failed to save build recordjava.io.IOException: java.lang.RuntimeException: Failed to serialize hudson.model.AbstractBuild#scm for class hudson.model.FreeStyleBuild at hudson.XmlFile.write(XmlFile.java:200) at hudson.model.Run.save(Run.java:2012) at hudson.model.Run.execute(Run.java:1873) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)Caused by: java.lang.RuntimeException: Failed to serialize hudson.model.AbstractBuild#scm for class hudson.model.FreeStyleBuild at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:256) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:224) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138) at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:209) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:150) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43) at com.thoughtworks.xstream.core.TreeMarshaller.start(TreeMarshaller.java:82) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.marshal(AbstractTreeMarshallingStrategy.java:37) at com.thoughtworks.xstream.XStream.marshal(XStream.java:1026) at com.thoughtworks.xstream.XStream.marshal(XStream.java:1015) at com.thoughtworks.xstream.XStream.toXML(XStream.java:988) at hudson.XmlFile.write(XmlFile.java:193) ... 5 moreCaused by: java.lang.RuntimeException: Failed to serialize org.jenkinsci.plugins.darcs.DarcsChangeLogParser#sanitizer for class org.jenkinsci.plugins.darcs.DarcsChangeLogParser at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:256) at
