Status: Resolved (View Workflow)
Windows Server 2008 R2, Jenkins installed as a service. Java version for Jenkins is 1.7.0.07-b11 (32 bit).
We've set up SVNKit in our Jenkins instance to use JNA to collect credentials for SVN access by setting -Dsvnkit.http.ntlm=jna in jenkins.xml. This has been working perfectly until we tried to upgrade Jenkins to 1.586, when the Jenkins JNA implementation was bumped to jna 4.10. After that, we get an "E200015: No credential to try." error.
The last working version was Jenkins 1.585 and subversion plugin 2.4.5. If I upgrade any of them, we get the error.
- depends on
JENKINS-28251 Subversion plugin consistent source of problems - allow native subversion client
JENKINS-27084 SVN authentication fails using subversion plugin v.2.5
- is duplicated by
JENKINS-26473 SVN cannot authenticate using Negotiate
I could solve a similar problem by setting the following JAVA option on jenkins startup:
It seems this issue is duplicate. Take a look JENKINS-27084.
schristou, What do you think if we resolve this ticket as duplicated?
This issue is a duplicate of JENKINS-27084 which was fixed in 2.5.1.
I'm having the same issue. My workaround is to use <exec> in ant and call svn directly from commandline. Eg:
Nevertheless I would love to see this bug fixed.