Tom Brus commented on Improvement JENKINS-18935

We have the same problem as Henri Gomez above:

...This client is too old to work with the working copy...

But the circumstances are slightly different:

  • I just upgraded the svn plugin from 2.4.5 to 2.5
  • my jobs that do not use a fresh workspace for svn work fine
  • my jobs that use a fresh copy fail as mentioned above
  • svn repos are taken from a dir on the same machine that runs jenkins (file:://...)
  • svn version installed on the machine is 1.7.9
  • in jenkins/configure the Subversion Workspace Version is set to 1.7

Even completely cleaning the workspace (including removing the .svn dir) does not solve this issue.

I did not revert to 2.4.5 yet, but I guess that will solve it. I also expect that upgrading the svn version on the machine to 1.8 will solve it.

When I do an 'svn status' on the dir on the disk from a shell I get the same error message. So my conclusion is that the working dir is created by the plugin as a 1.8 dir and then the locally installed svn (1.7.9) can not deal with that. So the plugin does not seem to listen to the setting Subversion Workspace Version which is set to 1.7.

Does this help?

I will go back to 2.4.5 until this is solved.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to