All geek questions in one place

Jenkins cannot use SVN credentials or upload new plugins / new versions

Can anyone suggest how to fix two problems?

- Unable to update Jenkins plugin and SVN

- Unable to connect to svn

I am configuring Jenkins on a 64bit Windows machine. It is configured to run as a Windows service.

We run this on 64-bit Windows 7

Jenkins 1.482

I can perform SVN update / verification from my user account on the machine.

When I try to set up a task on jenkins, I get the following when trying to add svn credentials

FAILED: org.tmatesoft.svn.core.SVNErrorMessage: svn: OPTIONS /svn/client/trunk failed

More details:

 FAILED: org.tmatesoft.svn.core.SVNErrorMessage: svn: OPTIONS /svn/client/trunk failed org.tmatesoft.svn.core.SVNException: svn: OPTIONS /svn/client/trunk failed at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:298) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:283) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:271) at ...

I stopped the service and started Jenkins from the command line and tried the same thing - with the same result.

I can connect to the svn server with the turtle client and through firefox with the same credentials.

In researching a problem, I saw several reports of similar problems, and the only one that seems to claim to fix it goes back to the Jenkins svn plugin version.

Then I tried installing the latest jenkins and Plugin for svn. Download failed. Yeah, I thought, obviously, a problem with the firewall. Therefore, I will disable the firewall.

Still no good. I cannot automatically download or get a new Jenkins or SVN plugin.

+6
source share
4 answers

Try running jenkins with this option:

 -Dsvnkit.http.sslProtocols="SSLv3"

Or, if Jenkins runs the svn plugin in a separate JVM, try adding the line to where the svn plugin launch configuration is.

This is a known issue with svnkit that is used by Jenkins svn plugin:

http://issues.tmatesoft.com/issue/SVNKIT-176

In addition, this answer may be useful regarding updating your svn plugin.

To change the Windows service command:

  • open cmd.exe command prompt window
  • sc qc "JenkinsSlave" (if this is the name of your service)
  • select and copy the value BINARY_PATH_NAME
  • change it by adding -Dsvnkit.http.sslProtocols=""SSLv3"" after the jar path - be aware of the double quote
  • sc config "JenkinsSlave" binPath= <paste the changed value copied earlier>

Replace JenkinsSlave with your service name.

+2
source

Windows 7 x64 has several options for the automatic firewall. You may need to open the firewall port to allow the connection.

You should be able to verify or eliminate this as a reason when trying to run your svn client outside of Jenkins.

+1
source

A bit late topic, but have you tried the following solution?

http://www.daangemist.nl/2014/03/03/jenkins-reports-sslv3-error-on-svn-update

what I developed with me, in my case I wanted to use -Dsvnkit.http.sslProtocols = "TLSv1"

+1
source

How about starting the Jenkins service in your account?

0
source

Source: https://habr.com/ru/post/926426/

More articles:


All Articles