• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • subversion-plugin
    • None

      Hi,

      I have:
      Jenkins 1.541
      Jenkins Subversion Plug-in 1.54
      Client SVN 1.8
      1 Master
      2 Slaves

      I configure my jobs for execute in a slave. In these slaves I have configured a VPN to connect slaves and repositories, but I can't configure this VPN in Master (security restrictions). When I execute my jobs, they download the code, but when finalizes the download, jenkins shows me the next error:

      Updating https://repositoryURL at revision '2013-12-09T00:00:00.000 +0000'
      U         file_1
      U         file_2
      U         ...
      U         file_n
      At revision 123456
      hudson.util.IOException2: revision check failed on https://repositoryURL
      	at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:178)
      	at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:113)
      	at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:654)
      	at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:815)
      	at hudson.model.AbstractProject.checkout(AbstractProject.java:1414)
      	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:652)
      	at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
      	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:561)
      	at hudson.model.Run.execute(Run.java:1677)
      	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
      	at hudson.model.ResourceController.execute(ResourceController.java:88)
      	at hudson.model.Executor.run(Executor.java:230)
      Caused by: org.tmatesoft.svn.core.SVNException: svn: E175002: OPTIONS /repositoryURL failed
      	at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:388)
      	at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373)
      	at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:361)
      	at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:707)
      	at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627)
      	at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102)
      	at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1020)
      	at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getLatestRevision(DAVRepository.java:180)
      	at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:118)
      	at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:148)
      	at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45)
      	at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:160)
      	at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35)
      	at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20)
      	at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1238)
      	at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294)
      	at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:967)
      	at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:872)
      	at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:166)
      	... 11 more
      Caused by: svn: E175002: OPTIONS /repositoryURL failed
      	at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208)
      	at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:154)
      	at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:97)
      	... 30 more
      Caused by: org.tmatesoft.svn.core.SVNException: svn: E175002: OPTIONS request failed on '/repositoryURL'
      svn: E175002: timed out waiting for server
      	at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64)
      	at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)
      	at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:777)
      	at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:382)
      	... 29 more
      Caused by: svn: E175002: OPTIONS request failed on '/repositoryURL'
      	at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208)
      	at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:775)
      	... 30 more
      Caused by: svn: E175002: timed out waiting for server
      	at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208)
      	at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:514)
      	... 30 more
      Caused by: java.net.SocketTimeoutException: connect timed out
      	at java.net.PlainSocketImpl.socketConnect(Native Method)
      	at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
      	at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
      	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
      	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
      	at java.net.Socket.connect(Socket.java:579)
      	at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:618)
      	at org.tmatesoft.svn.core.internal.util.SVNSocketFactory.connect(SVNSocketFactory.java:146)
      	at org.tmatesoft.svn.core.internal.util.SVNSocketFactory.createSSLSocket(SVNSocketFactory.java:106)
      	at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.connect(HTTPConnection.java:280)
      	at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:451)
      	... 30 more
      

      My jobs are launched when there are changes in the repositories.

      Can you help me?

          [JENKINS-20920] SVN failed after download the latest version

          amine bennani added a comment -

          I Met the same problem!
          My config Jenkins ver. 1.532.2 - plugin subversion 1.51

          And the job never complete the run. It just update (when it is necessary) then it fails.
          If there are no change with svn repository, the job succeed.
          So to complete my build, i run the job twice; a first time to make the update and a second one to complete the build.

          Does anyone have ever heard about such problem

          amine bennani added a comment - I Met the same problem! My config Jenkins ver. 1.532.2 - plugin subversion 1.51 And the job never complete the run. It just update (when it is necessary) then it fails. If there are no change with svn repository, the job succeed. So to complete my build, i run the job twice; a first time to make the update and a second one to complete the build. Does anyone have ever heard about such problem

          Oleg Nenashev added a comment -

          "java.net.SocketTimeoutException: connect timed out"

          Please check the correctness of the server's URL

          Oleg Nenashev added a comment - "java.net.SocketTimeoutException: connect timed out" Please check the correctness of the server's URL

          I have the same error, verified on jenkins 2.12 and 2.15.

          hudson.util.IOException2: revision check failed on https://svn
          ...
          Caused by: org.tmatesoft.svn.core.SVNException: svn: E175002: connection refused by the server
          svn: E175002: OPTIONS request failed on '/svn
          ...
          Caused by: java.net.ConnectException: Connection timed out: connect

          This happens whenever svn updates the workspace. Creating a workspace from scratch works fine, it's just the update that fails.

          Michiel Zweistra added a comment - I have the same error, verified on jenkins 2.12 and 2.15. hudson.util.IOException2: revision check failed on https://svn ... Caused by: org.tmatesoft.svn.core.SVNException: svn: E175002: connection refused by the server svn: E175002: OPTIONS request failed on '/svn ... Caused by: java.net.ConnectException: Connection timed out: connect This happens whenever svn updates the workspace. Creating a workspace from scratch works fine, it's just the update that fails.

          James Dumay added a comment -

          amine yaeger were you both trying to connect to a subversion repository that had poor or latent connectivity between the server and the Jenkins master?

          James Dumay added a comment - amine yaeger were you both trying to connect to a subversion repository that had poor or latent connectivity between the server and the Jenkins master?

          Ilya T added a comment - - edited

          Good Morning All
          i have the same issue on my
          Jenkins 2.73
          Jenkins Subversion Plug-in 2.9
          1 Master
          1 Slave

          In some security restrictions i can not setup vpn connection on master to external subversion repository, but on slave vpn works good and i'm trying to use slave for checkout.
          And i need run the job twice, to complete my build as well as Amine.
          Not sure but it seems that for some reason jenkins master will try to check/confirm code after update passed on slave.

          09:38:27 Updating https://**********/Project at revision 'some date'
          09:38:29 Using sole credentials *****/***** in realm ‘<https://*****:***> VisualSVN Server’
          09:38:32 U ************.cfg
          09:38:32 U ******\pom.xml
          09:38:32 U ******.xml
          09:38:32 U ******.xml
          09:38:32 U ******.xml
          09:38:32 U ******.xml
          09:38:33 At revision 122308
          09:38:33
          09:39:34 java.net.SocketTimeoutException: connect timed out
          09:39:34 at java.net.PlainSocketImpl.socketConnect(Native Method)
          09:39:34 at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
          09:39:34 at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
          09:39:34 at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
          09:39:34 at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
          09:39:34 at java.net.Socket.connect(Socket.java:589)
          09:39:34 at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:668)
          09:39:34 at org.tmatesoft.svn.core.internal.util.SVNSocketFactory.connect(SVNSocketFactory.java:162)
          09:39:34 at org.tmatesoft.svn.core.internal.util.SVNSocketFactory._createSSLSocket(SVNSocketFactory.java:122)
          09:39:34 at org.tmatesoft.svn.core.internal.util.SVNSocketFactory.createSSLSocket(SVNSocketFactory.java:92)
          09:39:34 at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.connect(HTTPConnection.java:275)
          09:39:34 at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:454)
          09:39:34 Caused: org.tmatesoft.svn.core.SVNException: svn: E175002: timed out waiting for server

          but next run

          09:56:37 Updating https://**********/Project_Re at revision '2017-08-08T09:55:37.096 +0300'
          09:56:39 Using sole credentials *****/***** in realm ‘<https://*****:***> VisualSVN Server’
          09:56:42 At revision 122312
          09:56:42
          09:56:43 [artif_deploy] $ cm . .. .... and job works as expected

          next time, job will failed after commin to svn and when i need to get new code i need to run my build twice (because build failed after checkout)

          will you be able to fix it?

          Ilya T added a comment - - edited Good Morning All i have the same issue on my Jenkins 2.73 Jenkins Subversion Plug-in 2.9 1 Master 1 Slave In some security restrictions i can not setup vpn connection on master to external subversion repository, but on slave vpn works good and i'm trying to use slave for checkout. And i need run the job twice, to complete my build as well as Amine. Not sure but it seems that for some reason jenkins master will try to check/confirm code after update passed on slave. 09:38:27 Updating https://**********/Project at revision 'some date' 09:38:29 Using sole credentials ***** / ***** in realm ‘< https://***** : *** > VisualSVN Server’ 09:38:32 U ************.cfg 09:38:32 U ******\pom.xml 09:38:32 U ******.xml 09:38:32 U ******.xml 09:38:32 U ******.xml 09:38:32 U ******.xml 09:38:33 At revision 122308 09:38:33 09:39:34 java.net.SocketTimeoutException: connect timed out 09:39:34 at java.net.PlainSocketImpl.socketConnect(Native Method) 09:39:34 at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) 09:39:34 at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) 09:39:34 at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) 09:39:34 at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) 09:39:34 at java.net.Socket.connect(Socket.java:589) 09:39:34 at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:668) 09:39:34 at org.tmatesoft.svn.core.internal.util.SVNSocketFactory.connect(SVNSocketFactory.java:162) 09:39:34 at org.tmatesoft.svn.core.internal.util.SVNSocketFactory._createSSLSocket(SVNSocketFactory.java:122) 09:39:34 at org.tmatesoft.svn.core.internal.util.SVNSocketFactory.createSSLSocket(SVNSocketFactory.java:92) 09:39:34 at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.connect(HTTPConnection.java:275) 09:39:34 at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:454) 09:39:34 Caused: org.tmatesoft.svn.core.SVNException: svn: E175002: timed out waiting for server but next run 09:56:37 Updating https://**********/Project_Re at revision '2017-08-08T09:55:37.096 +0300' 09:56:39 Using sole credentials ***** / ***** in realm ‘< https://***** : *** > VisualSVN Server’ 09:56:42 At revision 122312 09:56:42 09:56:43 [artif_deploy] $ cm . .. .... and job works as expected next time, job will failed after commin to svn and when i need to get new code i need to run my build twice (because build failed after checkout) will you be able to fix it?

          Oleg Nenashev added a comment -

          ilya_t probably you want to create a new ticket for it. I do not see how your comment is related to this ticket

          Oleg Nenashev added a comment - ilya_t probably you want to create a new ticket for it. I do not see how your comment is related to this ticket

          Ilya T added a comment -

          Hey Oleg, thanks for reply. I don't see any reasons to open a new one issue, because my issue is the same as on this ticket.

          I can provide full stacktrace and it's the same as we can see above.

          The issue is - each first checkout failed if since the previous one we had some commits. It's true for case when checkout scheduled for external svn repo on slave and slave has personal vpn connection to svn repo while master do not have this connection.

          Ilya T added a comment - Hey Oleg, thanks for reply. I don't see any reasons to open a new one issue, because my issue is the same as on this ticket. I can provide full stacktrace and it's the same as we can see above. The issue is - each first checkout failed if since the previous one we had some commits. It's true for case when checkout scheduled for external svn repo on slave and slave has personal vpn connection to svn repo while master do not have this connection.

            Unassigned Unassigned
            apiera Alex Piera
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: