-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Hudson 1.377, SVN Plugin 1.21, SVN repo v1.6, repo storage v1.4
I've run into a problem with Hudson where svn:externals appear to be checked out during a build, but when I examine the working directory the externals aren't actually there. The following is output from one of my failed builds:
Started by user anonymous Building remotely on build2 Cleaning workspace /opt/hudson/workspace/Shell Build Checking out http://repo/svn/vwc_repo/ShellScripts/trunk/softsys ...(typical svn output)... Fetching 'http://repo/svn/vwc_repo/ShellScripts/trunk/lib/bashLibrary.sh' at 13,135 into '/opt/hudson/workspace/Shell Build/softsys/bashLibrary.sh' At revision 13143 no change for http://repo/svn/vwc_repo/ShellScripts/trunk/softsys since the previous build no change for http://repo/svn/vwc_repo/ShellScripts/trunk/softsys/bashLibrary.sh since the previous build [Shell Build] $ /bin/sh -xe /tmp/hudson1416944625665584251.sh ...(execution of script)...
So it appears as though the external is checked out, however upon examining the working directory (directly and via extra lines in the running script) the external is not actually there.
Here is the definition of the external property on http://repo/svn/vwc_repo/ShellScripts/trunk/softsys:
http://repo/svn/vwc_repo/ShellScripts/trunk/lib/bashLibrary.sh@13135 bashLibrary.sh
Using SVN 1.6 I can check out the same directory and the external is properly retrieved.
I have the Subversion Workspace Version set to "1.6 (svn:externals to file)" and have the workspace cleaned on every build.
- is related to
-
JENKINS-17103 Apply credentials also to separate server used from svn:externals
- Open