Done:

jenkins@lucene1-us-west:~/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-5.3$ 
svnversion
1722449
jenkins@lucene1-us-west:~/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-5.3$

For now I don't touch the other jobs.

-----
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: Thursday, December 31, 2015 5:21 PM
> To: [email protected]
> Subject: RE: [JENKINS] Lucene-Solr-SmokeRelease-5.3 - Build # 1 - Failure
> 
> I don't want to bug them over new year holidays. It is still a pity that you
> cannot tell Jenkins to use a specific SVN version for each job. Unfortunately
> it’s a global setting (no idea why).
> 
> The easiest and quickest fix is to empty this workspace and once check it out
> with local svn, which I will do in a minute :-) Jenkins will then just update
> whats already there. I think we only need to do this for this job, right?
> 
> I will contact them as usual in chat on January 2nd :-)
> 
> Uwe
> 
> -----
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: [email protected]
> 
> 
> > -----Original Message-----
> > From: Steve Rowe [mailto:[email protected]]
> > Sent: Thursday, December 31, 2015 5:18 PM
> > To: [email protected]
> > Subject: Re: [JENKINS] Lucene-Solr-SmokeRelease-5.3 - Build # 1 - Failure
> >
> > Cool, thanks Uwe.  (Yes, I did start a new 5.3 build with an empty working
> > copy.  )
> >
> > Want me to contact infra?
> >
> > > On Dec 31, 2015, at 11:09 AM, Uwe Schindler <[email protected]> wrote:
> > >
> > > The reason why it works in the other builds is simple. The working copys
> > are existing there already. So jenkins does not update it (because its
> internal
> > svnkit can handle all svn formats, while command line only supports the
> > latest one). It only checks out new working copies in the newer Jenkins-
> > configured format.
> > >
> > > E.g. 5.x is old working copy format and works.
> > > uschindler@lucene1-us-west:/x1/jenkins/jenkins-
> > slave/workspace/Lucene-Solr-SmokeRelease-5.x$ svnversion
> > > 1722422
> > >
> > > I think you started a new 5.3 build with empty working copy?
> > > Other builds will break as soon as you nuke workspace.
> > >
> > > We have to ask Infra to update the locally installed svn as described
> before
> > and then nuke all working copies.
> > >
> > > 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: Thursday, December 31, 2015 5:05 PM
> > >> To: '[email protected]' <[email protected]>
> > >> Subject: RE: [JENKINS] Lucene-Solr-SmokeRelease-5.3 - Build # 1 -
> Failure
> > >>
> > >> It is exactly that problem:
> > >>
> > >> uschindler@lucene1-us-west:/x1/jenkins/jenkins-
> > slave/workspace/Lucene-
> > >> Solr-SmokeRelease-5.3$ svnversion
> > >> svn: The path '.' appears to be part of a Subversion 1.7 or greater
> > >> working copy.  Please upgrade your Subversion client to use this
> > >> working copy.
> > >>
> > >> uschindler@lucene1-us-west:/x1/jenkins/jenkins-
> > slave/workspace/Lucene-
> > >> Solr-SmokeRelease-5.3$ svn --version
> > >> svn, version 1.6.17 (r1128011)
> > >>   compiled Aug 13 2014, 20:41:52
> > >>
> > >> Copyright (C) 2000-2009 CollabNet.
> > >> Subversion is open source software, see http://subversion.apache.org/
> > >> This product includes software developed by CollabNet
> > >> (http://www.Collab.Net/).
> > >>
> > >> The following repository access (RA) modules are available:
> > >>
> > >> * ra_neon : Module for accessing a repository via WebDAV protocol
> using
> > >> Neon.
> > >>  - handles 'http' scheme
> > >>  - handles 'https' scheme
> > >> * ra_svn : Module for accessing a repository using the svn network
> > protocol.
> > >>  - with Cyrus SASL authentication
> > >>  - handles 'svn' scheme
> > >> * ra_local : Module for accessing a repository on local disk.
> > >>  - handles 'file' scheme
> > >>
> > >> I'll contact Infra to update the locally installed SVN version to be 
> > >> identical
> > to
> > >> Jenkins's internal one.
> > >>
> > >> 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: Thursday, December 31, 2015 5:01 PM
> > >>> To: [email protected]
> > >>> Subject: RE: [JENKINS] Lucene-Solr-SmokeRelease-5.3 - Build # 1 -
> Failure
> > >>>
> > >>> I'll check. The problem could be: Apache updated working copy format
> > of
> > >>> Jenkins (which checks out SVN with its internal, bundled svnkit
> > >>> implementation), but local SVN installation has different version - so 
> > >>> it
> > fails.
> > >>>
> > >>> We
> > >>>
> > >>> -----
> > >>> Uwe Schindler
> > >>> H.-H.-Meier-Allee 63, D-28213 Bremen
> > >>> http://www.thetaphi.de
> > >>> eMail: [email protected]
> > >>>
> > >>>> -----Original Message-----
> > >>>> From: Steve Rowe [mailto:[email protected]]
> > >>>> Sent: Thursday, December 31, 2015 4:55 PM
> > >>>> To: Lucene Dev <[email protected]>
> > >>>> Subject: Re: [JENKINS] Lucene-Solr-SmokeRelease-5.3 - Build # 1 -
> > Failure
> > >>>>
> > >>>> I don’t understand what happened here - this is the section of
> > common-
> > >>>> build.xml where the error is printed, when the output from
> svnversion
> > >>>> includes one of the sequences ‘exported’ or ‘unversioned’:
> > >>>>
> > >>>> ——
> > >>>> <macrodef name="get-svn-info"
> > >>>>          description="Populates properties svn.URL and svn.Revision
> using
> > >> 'svn
> > >>>> info'.">
> > >>>>  <attribute name="directory"/>
> > >>>>  <sequential>
> > >>>>    <exec dir="@{directory}" executable="${svnversion.exe}"
> > >>>> outputproperty="svn.ver"/>
> > >>>>    <fail message="A subversion checkout is required for this target">
> > >>>>      <condition>
> > >>>>        <matches pattern="(exported|unversioned.*)"
> string="${svn.ver}"
> > >>>> casesensitive="false"/>
> > >>>>      </condition>
> > >>>>    </fail>
> > >>>> ——
> > >>>>
> > >>>> The error happens when <svn-export-source> is called for the
> Lucene
> > >>> source
> > >>>> dir from lucene/build.xml:
> > >>>>
> > >>>> ——
> > >>>> <target name="package-tgz-src" depends="init-dist"
> > >>>>        description="--> Generates the Lucene source distribution from
> > 'svn
> > >>>> export' as .tgz">
> > >>>>  <property name="source.package.file"
> > >>>>            value="${dist.dir}/lucene-${version}-src.tgz"/>
> > >>>>  <delete file="${source.package.file}"/>
> > >>>>  <svn-export-source source.dir=".”/>
> > >>>> ——
> > >>>>
> > >>>> Only thing I can think of is that somehow the current directory used
> by
> > >>> <svn-
> > >>>> export-source source.dir=“.”> isn’t set properly because of how
> > Jenkins
> > >>>> invokes Ant?  But this should be a problem for every other Jenkins
> job
> > >>>> running ‘ant nightly-smoke’...
> > >>>>
> > >>>> I got past this point when I ran ‘ant -
> > >>>> DsmokeTestRelease.java8=$JAVA8_HOME nightly-smoke’ on my
> > laptop
> > >>>> (same cmdline used by Jenkins), but my Ant is too new (1.9 vs 1.8), so
> it
> > >>>> failed, later in the process (when checking jar metadata for correct
> Ant
> > >>>> version).
> > >>>>
> > >>>> Uwe, do you have any ideas?
> > >>>>
> > >>>>> On Dec 31, 2015, at 9:54 AM, Apache Jenkins Server
> > >>>> <[email protected]> wrote:
> > >>>>>
> > >>>>> Build: https://builds.apache.org/job/Lucene-Solr-SmokeRelease-
> > 5.3/1/
> > >>>>>
> > >>>>> No tests ran.
> > >>>>>
> > >>>>> Build Log:
> > >>>>> [...truncated 17960 lines...]
> > >>>>> BUILD FAILED
> > >>>>> /x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-
> > >>>> 5.3/build.xml:461: The following error occurred while executing this
> > line:
> > >>>>> /x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-
> > >>>> 5.3/lucene/build.xml:344: The following error occurred while
> executing
> > >> this
> > >>>> line:
> > >>>>> /x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-
> > >>>> 5.3/lucene/common-build.xml:2270: The following error occurred
> while
> > >>>> executing this line:
> > >>>>> /x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-
> > >>>> 5.3/lucene/common-build.xml:2288: A subversion checkout is
> required
> > >> for
> > >>>> this target
> > >>>>>
> > >>>>> Total time: 4 minutes 10 seconds
> > >>>>> Build step 'Invoke Ant' marked build as failure
> > >>>>> Email was triggered for: Failure - Any
> > >>>>> Sending email for trigger: Failure - Any
> > >>>>> Setting LATEST1_8_HOME=/home/jenkins/jenkins-
> > >>>> slave/tools/hudson.model.JDK/latest1.8
> > >>>>> Setting LATEST1_8_HOME=/home/jenkins/jenkins-
> > >>>> slave/tools/hudson.model.JDK/latest1.8
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> ---------------------------------------------------------------------
> > >>>>> 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]
> > >
> >
> >
> > ---------------------------------------------------------------------
> > 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]

Reply via email to