Jenkins also fixes the Clover.xml problems affecting almost every clover-enabled build (hopefully): https://github.com/lacostej/jenkins/commit/31b8361d3152fb7970e1c11c906a763fa 1aa5c25 (see also attached issue mail arriving here few minutes ago). It's very important to fix this ASAP, as we have broken builds because of this bug since months!
I don't know what the best way to handle this is. Maybe we patch our latest Hudson with the supplied patch? Uwe ----- Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -----Original Message----- > From: Niklas Gustavsson [mailto:nik...@protocol7.com] > Sent: Thursday, February 03, 2011 2:39 PM > To: builds@apache.org > Subject: Re: Questions : install Jenkins instead of Hudson > > On Thu, Feb 3, 2011 at 2:28 PM, Olivier Lamy <ol...@apache.org> wrote: > > * which code branch do we have to follow ( Jenkins or Oracle : IMHO > > the most active is the Jenkins one) > > Time will tell, but I'm betting on the Jenkins branch. Jenkins has released a > 1.396 release which contains a fix for JNPL slaves not reconnecting correctly. > This is a problem we currently have with our Windows slave and that I would > see fixed. So, unless anyone objects, I will look into upgrading to Jenkins > 1.396 in the near future. > > > * do we have to rename hudson.apache.org to jenkins.apache.org > > In my opinion, this has low priority. The major reason for renaming would > probably be to make a stand in the Hudson vs Jenkins situation. > > /niklas
--- Begin Message ---[ http://issues.jenkins-ci.org/browse/JENKINS-7836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=145414#comment-145414 ] lacostej commented on JENKINS-7836: ----------------------------------- If you are affected by this problem and aren't afraid of patching&build from source, you might want to try https://github.com/lacostej/jenkins/commit/31b8361d3152fb7970e1c11c906a763fa1aa5c25 I will try making a test build for those who want to test it. > Clover and cobertura parsing on hudson master fails because of invalid XML > -------------------------------------------------------------------------- > > Key: JENKINS-7836 > URL: http://issues.jenkins-ci.org/browse/JENKINS-7836 > Project: Jenkins > Issue Type: Bug > Components: clover, cobertura > Affects Versions: current > Reporter: thetaphi > Assignee: Kohsuke Kawaguchi > Priority: Critical > Attachments: HUDSON-7836-stacktrace.txt > > > Since a few days, on our Apache Hudson installation, parsing of Clover's > clover.xml or the Coberture's coverage.xml file fails (but not in all cases, > sometimes it simply passes with the same build and same job configuration). > This only happens after transferring to master, the reports and xml file is > created on Hudson slave. It seems like the network code somehow breaks the > xml file during transfer to the master. > Downloading th clover.xml from the workspace to my local computer and > validating it confirms, that it is not incorrectly formatted and has no XML > parse errors. > - Here are errors that appear during clover publishing: > [https://hudson.apache.org/hudson/job/Lucene-trunk/1336/console] > - For cobertura: > [https://hudson.apache.org/hudson/view/Directory/job/dir-shared-metrics/34/console] -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
--- End Message ---
