Jenkins Build not working with SVNException

Question

I am trying to run jenkins build. Below is my configuration.

Jenkins Version: 1.445
Deployment: like WAR Java: 1.7 (server 64 bit)
Tomcat Ver: 7.0.23

It produces the following error:

Started by user jenkins-admin Updating https://myrepo.mycompany.com/svn/repos/myrepo ERROR: Failed to update https://myrepo.mycompany.com/svn/repos/myrepo org.tmatesoft.svn.core.SVNException: svn: OPTIONS /svn/repos/myrepo 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 org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:533) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:98) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1011) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getRepositoryUUID(DAVRepository.java:148) at org.tmatesoft.svn.core.wc.SVNBasicClient.createRepository(SVNBasicClient.java:342) at org.tmatesoft.svn.core.wc.SVNBasicClient.createRepository(SVNBasicClient.java:330) at org.tmatesoft.svn.core.wc.SVNUpdateClient.update(SVNUpdateClient.java:535) at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:401) at hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:135) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:136) at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:787) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:768) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:752) at hudson.FilePath.act(FilePath.java:783) at hudson.FilePath.act(FilePath.java:765) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:742) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:684) at hudson.model.AbstractProject.checkout(AbstractProject.java:1195) at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:571) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:460) at hudson.model.Run.run(Run.java:1404) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:481) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:238) Caused by: org.tmatesoft.svn.core.SVNErrorMessage: svn: OPTIONS /svn/repos/myrepo failed at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:200) at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:146) at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:89) ... 27 more Caused by: org.tmatesoft.svn.core.SVNException: svn: OPTIONS request failed on '/svn/repos/myrepo' svn: unknown host at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) 

The problem is that it does not interrupt all the time. However, he does not cope in 70-80% of cases. The credentials and url for svn repo are correct.

UPDATE . I have tried all the possibilities now. The problem persists. I tried with JDK 6 (both 32 and 64 bit). The problem is not coming.

I am working on RHEL 5.6. Can anybody help?

Answer 1

I noticed this line:

 Caused by: org.tmatesoft.svn.core.SVNException: svn: OPTIONS request failed on '/svn/repos/myrepo' svn: unknown host 

Whenever I have a problem with Jenkins, I log in to Jenkins when the user starts Jenkins, go to the working directory inside Jenkins and try to do everything that Jenkins does from the command line (for example, updating my working directory). This usually helps you indicate a specific error.

Try updating several times from the Jenkin job's working directory and see if you get the same error. If you do this, this may indicate a network problem (unknown host).

If you can run updates from the working directory of your Jenkins server in the working directory of the job, the problem could be SVNKit itself. What version of Subversion and SVNKit are you using?

Try deleting the working directory and see if checking it helps.

Answer 2

I noticed this error after updating my "Jenkins Subversion Plugin" from version 1.42 to version 1.44.

To fix: Please check the "Jenkins Subversion plugin" version, if it is v1.44, upgrade to a lower version.

It looks like we have some problems with the new Subversion plugin.

Answer 3

node starting the assembly cannot resolve the host name. Perhaps the full name is required: instead of mysvnbox, something like mysvnbox.mydomain.com; Or perhaps node is blocked by a firewall. The fact that it works seems to indicate that at least one node has visibility or can use a shorthand domain specification. Good luck.

Answer 4

I ran into the same problem in Jenkins. When checking the code, it did not work. I tried to increase Jenkins workspace, but crowd authentication was suggested. It could not be updated, and I tried to clear the authentication date from disruptive work and restart my build server (you can log out of your credentials and log in). This will work.