Hi Narahari, The version of svnkit used in the jenkins subversion plugin only supports up to subversion 1.7 workspace.
So you have a few possible solutions: 1) update and test the plugin and send a pull request 2) downgrade your native svn client to 1.7 3) configure maven to use the java svn client not the native one (https://code.google.com/a/apache-extras.org/p/maven-scm-provider-svnjava/). I would say by far the quickest to get you going is option 2 - the best option being option 1. Regards /James On Monday, 3 November 2014 02:03:02 UTC, Narahari 'n' Savitha wrote: > > Friends: > > This issue might have been hashed and rehashed but I could not find an > answer. > My setup > > Jenkins 1.587 > Subversion plugin is 2.2 but it shows the max SVN version in Manage > Jenkins to be 1.7 > Subversion client on the machine is 1.8.1 > > I use Maven for our projects and we use the maven release plugin that uses > the command line svn client. > > In the project we have jenkins checking out the code with the 1.7 version > of svn. > > The maven release plugin comes in but the svn version of command line > 1.8.1 and this caused issues with svn upgrade errors. > > So how do we make subversion plugin have the latest subversion client > software as in svn 1.8.1 ? > > Please don't tell me that my option is to not use the inbuilt plugin but > command line client through out. > > -Narahari > > -- 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/d/optout.
