• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • subversion-plugin
    • 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.

          [JENKINS-8312] svn:externals not being checked out

          Nat Stein added a comment -

          Same issue: svn:externals are not checked out. All source is on the same server with the same credentials. Does anyone have a workaround? This is quite an obstacle for us.

          (Jenkins 1.429 / Subversion plugin 1.42)

          Nat Stein added a comment - Same issue: svn:externals are not checked out. All source is on the same server with the same credentials. Does anyone have a workaround? This is quite an obstacle for us. (Jenkins 1.429 / Subversion plugin 1.42)

          We found that if you also create a Job for the external submodule and specify the SVN credentials for that one, then the other job referencing this submodule is staring to be able to check out this repo as well.

          Oliver Drobnik added a comment - We found that if you also create a Job for the external submodule and specify the SVN credentials for that one, then the other job referencing this submodule is staring to be able to check out this repo as well.

          Peter Gruener added a comment -

          Same here. Jenkins 1.466.2, subversion plugin 1.43. Also creating external submodule and specifying credentials there does not work.

          Peter Gruener added a comment - Same here. Jenkins 1.466.2, subversion plugin 1.43. Also creating external submodule and specifying credentials there does not work.

          Juan Alvarez added a comment -

          This worked for me: go to <jenkins_server>/scm/SubversionSCM/enterCredential and put the credentials for the external repository there.
          Then I deleted the repository and launch the build again (I don't know if it works for an update operation).
          Hope this helps!
          Juan M.

          Juan Alvarez added a comment - This worked for me: go to <jenkins_server>/scm/SubversionSCM/enterCredential and put the credentials for the external repository there. Then I deleted the repository and launch the build again (I don't know if it works for an update operation). Hope this helps! Juan M.

          Henry Chan added a comment -

          Try
          Menu->Manage Jenkins->Configure System->Subversion->Subversion Workspace Version
          assign to 1.7 (i think the default is 1.4)

          Henry Chan added a comment - Try Menu->Manage Jenkins->Configure System->Subversion->Subversion Workspace Version assign to 1.7 (i think the default is 1.4)

          zeliff added a comment -

          Problem still exists in Jenkins 1.563, Subversion plugin 2.2. The workarounds described by Henry Chan and Jack Ace do not work.

          zeliff added a comment - Problem still exists in Jenkins 1.563, Subversion plugin 2.2. The workarounds described by Henry Chan and Jack Ace do not work.

          Daniel Beck added a comment -

          zeliff: Likely related to JENKINS-21785 as of Subversion plugin 2.x. Try specifying Additional Credentials as described there. Also, note that externals are generally rather broken before 2.3.

          Given the massive changes to SVN auth in 2.0, I'm inclined to close this unless it is confirmed to still occur in 2.x. Does anyone object?

          Daniel Beck added a comment - zeliff : Likely related to JENKINS-21785 as of Subversion plugin 2.x. Try specifying Additional Credentials as described there. Also, note that externals are generally rather broken before 2.3. Given the massive changes to SVN auth in 2.0, I'm inclined to close this unless it is confirmed to still occur in 2.x. Does anyone object?

          Oleg Nenashev added a comment -

          Marking as resolved.
          If somebody experiences the issue with the properly configured installation, please re-open the issue

          Oleg Nenashev added a comment - Marking as resolved. If somebody experiences the issue with the properly configured installation, please re-open the issue

          Fabien Carmagnac added a comment - - edited

          Hi, I have the same problem.
          The external is in the same svn tree.
          in the svn :

          /a/b/c/foo.txt
          /a/d/e/f/foo.txt <== external to /a/b/c/foo.txt

          updating a/d/e does not update /a/d/e/f/foo.txt when /a/b/c/foo.txt has been updated.

          I have no throw inside jenkins.err.log.

          Jenkins ver : 1.647
          svn plugin (https://wiki.jenkins-ci.org/display/JENKINS/Subversion+Plugin) : 2.5.7
          os : win server 2008 R2
          client used to attach externals : tortoise 1.9

          Fabien Carmagnac added a comment - - edited Hi, I have the same problem. The external is in the same svn tree. in the svn : /a/b/c/foo.txt /a/d/e/f/foo.txt <== external to /a/b/c/foo.txt updating a/d/e does not update /a/d/e/f/foo.txt when /a/b/c/foo.txt has been updated. I have no throw inside jenkins.err.log. Jenkins ver : 1.647 svn plugin ( https://wiki.jenkins-ci.org/display/JENKINS/Subversion+Plugin ) : 2.5.7 os : win server 2008 R2 client used to attach externals : tortoise 1.9

          Michael Smith added a comment -

          Possibly worth mentioning, had a fresh Jenkins installation today and I was banging my head into the wall trying to see what the problem was (latest jenkins and plugins)..... turns out it was the silly little 'ignore externals' checkbox in the SVN config of the job itself. Make sure you're not a dummy like me

          Michael Smith added a comment - Possibly worth mentioning, had a fresh Jenkins installation today and I was banging my head into the wall trying to see what the problem was (latest jenkins and plugins)..... turns out it was the silly little 'ignore externals' checkbox in the SVN config of the job itself. Make sure you're not a dummy like me

            Unassigned Unassigned
            matt__ matt__
            Votes:
            14 Vote for this issue
            Watchers:
            18 Start watching this issue

              Created:
              Updated: