Using Jenkins to Commit to SVN 1.8

[Eric]

Hi,

I'm new to Jenkins and having one issue. Currently, I'm using the "Promote Build" Plugin. When I promote a build, I execute a batch command to commit a text file back into the repository. This is only done when I promote a build. However, its SVN 1.8.8. Searching around I see that Jenkins doesn't support 1.8. Is there currently a way to work around this?

Here is how I commit to the repository:

svn upgrade

svn update Test

svn commit -m "Text File from Build Number: %BUILD_NUMBER% "

The first time I do a build it works fine, however the second time I get this error:

 ERROR: svn: E155021: This client is too old to work with the working copy at
'C:\Users\user\.jenkins\jobs\Hello World Test\workspace' (format '31').
org.tmatesoft.svn.core.SVNException: svn: E155021: This client is too old to work with the working copy at
'C:\Users\user\.jenkins\jobs\Hello World Test\workspace' (format '31').

Thanks 

[Daniel Beck]

On 15.07.2014, at 16:27, Eric <ericlee...@gmail.com> wrote:

> Is there currently a way to work around this?

* Don't use the SVN 1.8 client when modifying the Jenkins SVN checkout (is there _really_ a reason to upgrade the client, other than the new version existing?).
* Have the Workspace Cleanup plugin remove the workspace before or after the build so you're always working with a fresh checkout. The Subversion plugin's strategy 'Always checkout a new copy' might also work.