SVN "not under version control" with Jenkins

Question

I have a project in Jenkins that has many SVN repositories. Whenever I build, the first build after cleaning up the workspace fails with errors like the one below. Without changing anything, the next build will succeed.

If I set the project to always clear the workspace before building, it will always fail. Each time, with different SVN repositories.

I tried upgrading to SVN 1.6, tried to verify that the HTTPS certificate was ok, not sure what else to look for?

ERROR: Failed to parse svn info for https://subversion.assembla.com/svn/<PROJECT NAME HIDDEN>/trunk org.tmatesoft.svn.core.SVNException: svn: '/tmp/data/hudson/jobs/Build_ISO/workspace/ch.ethz.ssh2' is not under version control 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.wc.SVNWCClient$13.handleError(SVNWCClient.java:3314) at org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.walkEntries(SVNWCAccess.java:758) at org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.walkEntries(SVNWCAccess.java:741) at org.tmatesoft.svn.core.wc.SVNWCClient.crawlEntries(SVNWCClient.java:3294) at org.tmatesoft.svn.core.wc.SVNWCClient.doInfo(SVNWCClient.java:2498) at org.tmatesoft.svn.core.wc.SVNWCClient.doInfo(SVNWCClient.java:2865) at hudson.scm.SubversionSCM$BuildRevisionMapTask.invoke(SubversionSCM.java:1023) at hudson.scm.SubversionSCM$BuildRevisionMapTask.invoke(SubversionSCM.java:1001) at hudson.FilePath.act(FilePath.java:832) at hudson.FilePath.act(FilePath.java:814) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:685) at hudson.model.AbstractProject.checkout(AbstractProject.java:1212) at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:579) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:468) at hudson.model.Run.run(Run.java:1410) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:238) Caused by: org.tmatesoft.svn.core.SVNErrorMessage: svn: '/tmp/data/hudson/jobs/Build_ISO/workspace/ch.ethz.ssh2' is not under version control at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:163) at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:118) ... 17 more 

Answer 1

I know that the thread is out of date and almost out of date, but it has not stopped from people like me, landing here, in search of a solution to this popular Jenkins problem. So now the problem is solved. I am posting an answer for future use: -

An initial search gives this problem due to an error in some version of the SVN plugin, so the obvious solution is to change this plugin, the same is indicated in the links given by @ChrisH. His links were a great help. Thus, you can update the svn plugin using the following two methods: -

• Go to plugin management and install the update there.
• Download the * .hpi file from this link and put the * .hpi file in the $ JENKINS_HOME / plugins / folder. If you do not know where the $ JENKINS_HOME folder is located than most chances are, it will be a hidden folder in your home directory (for Linux).

After updating the plugin, you need to restart the Jenkins so that the new plugin can take effect.

However, if you recently downloaded jenkins, you may not need to follow the above process. Just go to Jenkins-> Configure System Management and change the version of SVN (to version 1.6) in the combo box.

Good luck

Answer 2

If you have any svn: externals links in your repository, you may encounter one of the following problems:

• JENKINS-3673
• JENKINS-11806

Answer 3

I had a similar problem when I browsed through the first repository using the module name and the second repository named "." (without module name). The second check was overwritten by the first.

The solution that worked for me was this: first check the module name repository (there can only be one), and then the non-module name repositories.

Answer 4

If I understood your settings correctly, you have several SVN URLs and would like to check these URLs for a set of folders in the jenkins project workspace. Something like me here:

If you do not define the local module directory, then this will be the workspace. And I think that if your checks contain overlapping directories, you might have a problem. Therefore, always do separate checks within the same project by setting the module directory. Then you need to customize your assembly to match.

Answer 5

Here is another possibility: inconsistent URLs in your svn: externals properties. I just defined this in my current project: external . (above) all testmachine-01 links, but external links in the Server directory are indicated by testmachine-01.companydomain.com , and this was solved in one way on my development machine and in another on the build server.