Nice solution, thanks Uwe! On Wed, Mar 7, 2012 at 2:43 AM, Uwe Schindler <[email protected]> wrote: > I opened https://issues.apache.org/jira/browse/INFRA-4521 for that. > > ----- > Uwe Schindler > H.-H.-Meier-Allee 63, D-28213 Bremen > http://www.thetaphi.de > eMail: [email protected] > > >> -----Original Message----- >> From: Uwe Schindler [mailto:[email protected]] >> Sent: Wednesday, March 07, 2012 8:20 AM >> To: [email protected] >> Subject: RE: [JENKINS] Lucene-trunk - Build # 1851 - Failure >> >> Problem solved. The Jenkins slave is now using SVN 1.6.17. 1.7 port was >> uninstalled to prevent command-path clashes (/etc/alternatives or whatever). >> >> I will ask now infra and builds about their plans to upgrade the Jenkins >> system >> to SVN 1.7, until that time we are fine with the old version. >> >> Uwe >> >> ----- >> Uwe Schindler >> H.-H.-Meier-Allee 63, D-28213 Bremen >> http://www.thetaphi.de >> eMail: [email protected] >> >> >> > -----Original Message----- >> > From: Uwe Schindler [mailto:[email protected]] >> > Sent: Wednesday, March 07, 2012 8:16 AM >> > To: [email protected] >> > Subject: RE: [JENKINS] Lucene-trunk - Build # 1851 - Failure >> > >> > Hi Robert, >> > >> > I was expecting this problem, but I have not seen any builds running that >> exec. >> > In my opinion it’s a bad idea to use different versions of tools and >> > in general calling the svnversion command from within a checkout or at >> > least don’t enforce it to complete (what happens if you have no >> > checkout at all? In that case Lucene also builds?). This is a problem >> > here because Jenkins does not use the system SVN to checkout but the >> > own Java-based bundled one. Means, the checkouts are only useable by >> > Jenkins itself. Using svnversion from the code inside our build script >> > conflicts and the svn export does not work (because revno is unknown). >> > >> > For now I will downgrade SVN to 1.6 on our box (build is currently running: >> > make deinstall on subversion port, make install on subversion16 port) >> > I will ask builds@ao, what they think about upgrading Jenkins-SVN >> > (maybe Tmatesoft does not have a new client available - that's what I >> expect?). >> > >> > Uwe >> > >> > ----- >> > Uwe Schindler >> > H.-H.-Meier-Allee 63, D-28213 Bremen >> > http://www.thetaphi.de >> > eMail: [email protected] >> > >> > > -----Original Message----- >> > > From: Robert Muir [mailto:[email protected]] >> > > Sent: Wednesday, March 07, 2012 5:21 AM >> > > To: [email protected] >> > > Subject: Re: [JENKINS] Lucene-trunk - Build # 1851 - Failure >> > > >> > > My approach didn't work: it seems jenkins has its own older svn >> > > client that is conflicting with the svn on the system itself >> > > (/usr/local/bin). >> > > >> > > So despite upgrading all the checkouts, i see: >> > > >> > > Checking out a fresh workspace because Jenkins failed to detect the >> > > current workspace >> > > /usr/home/hudson/hudson-slave/workspace/Lucene-Solr-tests-only- >> > > trunk-java7/checkout >> > > ERROR: svn: The path >> > > '/usr/home/hudson/hudson-slave/workspace/Lucene-Solr-tests-only-trun >> > > k- >> > > java7/checkout' >> > > appears to be part of a Subversion 1.7 or greater working copy. >> > > Please upgrade your Subversion client to use this working copy. >> > > org.tmatesoft.svn.core.SVNException: svn: The path >> > > '/usr/home/hudson/hudson-slave/workspace/Lucene-Solr-tests-only-trun >> > > k- >> > > java7/checkout' >> > > appears to be part of a Subversion 1.7 or greater working copy. >> > > Please upgrade your Subversion client to use this working copy. >> > > >> > > So its nuked all my efforts to upgrade these checkouts. >> > > >> > > We must either upgrade this "jenkins-svn" to 1.7, or downgrade our >> > > system svn (e.g. install ports/devel/subversion16 instead). >> > > >> > > I'll wait and see what Uwe thinks... >> > > >> > > On Tue, Mar 6, 2012 at 10:46 PM, Robert Muir <[email protected]> >> wrote: >> > > > The issue is that svn was upgraded to 1.7. I'm svn upgrade'ing all >> checkouts. >> > > > >> > > > On Tue, Mar 6, 2012 at 10:30 PM, Chris Hostetter >> > > > <[email protected]> wrote: >> > > >> >> > > >> : Build: https://builds.apache.org/job/Lucene-trunk/1851/ >> > > >> : >> > > >> : No tests ran. >> > > >> >> > > >> Looks like same problem as the 3x branch: exec of svnversion is >> > > >> failing, which makes me suspicious that it isn't in the path. >> > > >> >> > > >> >> > > >> -Hoss >> > > >> >> > > >> ----------------------------------------------------------------- >> > > >> -- >> > > >> -- To unsubscribe, e-mail: [email protected] For >> > > >> additional commands, e-mail: [email protected] >> > > >> >> > > > >> > > > >> > > > >> > > > -- >> > > > lucidimagination.com >> > > >> > > >> > > >> > > -- >> > > lucidimagination.com >> > > >> > > -------------------------------------------------------------------- >> > > - To unsubscribe, e-mail: [email protected] For >> > > additional commands, e-mail: [email protected] >> > >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [email protected] For >> > additional commands, e-mail: [email protected] >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] For additional >> commands, e-mail: [email protected] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >
-- lucidimagination.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
