SVNKit will work happily on 1.4, 1.5 and 1.6 working copies IIRC, now it may upgrade them to 1.7 as soon as it sees them, or it may not. I have not verified so cannot comment.
On 23 April 2013 15:29, David Aldrich <[email protected]> wrote: > Hi Stephen**** > > ** ** > > Thanks very much for your explanation. That is very clear.**** > > ** ** > > Do you know what happens when one upgrades from 1.39 to 1.45? If one was > using a svn command line client, the client would warn you that the working > copy needs upgrading and one could run ‘svn upgrade’ on it. What would be > the procedure for Jenkins working copies? Should I upgrade each working > copy manually from the command line or else the Jenkins jobs will fail?*** > * > > ** ** > > BR**** > > ** ** > > David**** > > ** ** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Stephen Connolly > *Sent:* 23 April 2013 15:24 > *To:* [email protected] > > *Subject:* Re: Will next LTS use svn v1.7?**** > > ** ** > > https://github.com/jenkinsci/jenkins/blob/stable/war/pom.xml#L291**** > > ** ** > > indicates that subversion plugin 1.39 is bundled in 1.509.1, which IIRC > was the last release before SVNKit changed to a more viral license.**** > > ** ** > > I don't know what the story is with whether OSS is going to bundle the > newer subversion plugin or not. I do know that the license is such that we > cannot bundle it within Jenkins Enterprise though, so we have to leave it > up to customers to download and install the plugin themselves.**** > > ** ** > > There is nothing preventing you from upgrading the Subversion plugin to > the latest on any version of Jenkins that is compatible with the latest > version of the Subversion plugin.**** > > ** ** > > In other words, as long as you are on Jenkins 1.466 or newer, you can > upgrade that Jenkins to 1.45 of the Subversion plugin and that works with > Subversion 1.7.**** > > ** ** > > Out of the box (as it were) Jenkins OSS comes with a version of the > Subversion plugin that uses the Subversion 1.6 client protocol, so it can > check out and commit from/to 1.7 subversion servers but it cannot use 1.7 > working copies. **** > > ** ** > > HTH**** > > ** ** > > On 23 April 2013 12:47, Mark Waite <[email protected]> wrote:**** > > I read the history incorrectly. It appears that Subversion 1.7 support > was introduced into the Subversion plugin in May 2012, not Jan 2013. That > was well before the Nov 2012 release of the most recent long term support > release, Jenkins 1.480.1. As far as I can tell, the current Jenkins LTS, > 1.480.3, already supports Subversion 1.7.**** > > ** ** > > Mark Waite**** > > > > On Tuesday, April 23, 2013 5:39:39 AM UTC-6, Mark Waite wrote:**** > > As far as I can guess from reading the history of the Subversion plugin on > the Jenkins wiki, it appears that Subversion 1.7 support was included in > Jan 2013, while Jenkins 1.509 was released in April 2013. I think that > suggests Subversion 1.7 support will be included in Jenkins 1.509.1.**** > > ** ** > > If you'd like suggestions on a fast way to install and configure a test > Jenkins on your own desktop Windows machine, I made a screencast called > "Jenkins in 5 minutes" that might be helpful. Refer to > http://bit.ly/jenkins-in-five-minutes for the screencast. The screencast > is only 5 minutes. That 5 minutes includes downloading Jenkins, starting > Jenkins, configuring a Subversion based Jenkins job, and running that > Subversion based Jenkins job successfully.**** > > ** ** > > Thanks,**** > > Mark Waite > > On Tuesday, April 23, 2013 1:55:45 AM UTC-6, David Aldrich wrote:**** > > Hi Mark**** > > **** > > Thanks for your reply. It would require quite a lot of work to set up a > test instance of Jenkins and to test the Subversion plugin with the new > LTS. I’m sorry, but we don’t have the resources to do that currently.**** > > **** > > Thanks for your hard work in contributing to the LTS releases.**** > > **** > > Best regards**** > > **** > > David**** > > **** > > *From:* [email protected] > [mailto:[email protected]<[email protected]>] > *On Behalf Of *Mark Waite > *Sent:* 22 April 2013 17:29 > *To:* [email protected] > *Subject:* Re: Will next LTS use svn v1.7?**** > > **** > > I created that link based on the contents of the previous LTS release page > (1.480.x RC Testing). I did not intend to make it a statement of what > features were included or not included in the 1.509.x LTS release.**** > > **** > > Would you be willing to download the 1.509.1 LTS release candidate, > perform some Subversion 1.7 specific testing, and note the results of that > testing on the Wiki page?**** > > **** > > That would answer your question, assist with the LTS testing, and help the > Jenkins user community.**** > > **** > > Thanks,**** > > Mark Waite**** > > **** > ------------------------------ > > *From:* David Aldrich <[email protected]> > *To:* "[email protected]" <[email protected]> > *Sent:* Monday, April 22, 2013 7:29 AM > *Subject:* Will next LTS use svn v1.7?**** > > **** > > Hi**** > > **** > > I was hoping that the next Jenkins LTS release will use a Subversion v.1.7 > compatible svn plugin, but this link suggests that it will still use a > v.1.6 compatible version:**** > > **** > > https://wiki.jenkins-ci.org/display/JENKINS/LTS+1.509.x+RC+Testing<https://wiki.jenkins-ci.org/display/JENKINS/LTS+1.480.x+RC+Testing> > **** > > **** > > Does anyone have any comment please?**** > > **** > > Best regards**** > > **** > > David**** > > **** > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > **** > > **** > > **** > > Click > here<https://www.mailcontrol.com/sr/GO1NJvAL5o7GX2PQPOmvUhe0y89+yNqhg+dId!tvIV2f65MFOEy1Ob6g!YgnEnQE8zrIqO5KosF+U88fPeCTtg==>to > report this email as spam. > **** > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > **** > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > **** > > ** ** > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > **** > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
