Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-4175

regression between 1.309 and 1.318: svn can't checkout twice per project

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • subversion-plugin
    • None
    • Platform: All, OS: Windows XP

      Looks like this fix may have broken checking out two directories with the same
      authenticaiton? I upgraded from 1.309 to 1.318 yesterday, and was previously
      able to configure two svn checkouts on one job:

      https://foo.com/project/bar
      to directory bar

      and

      https://foo.com/project/baz
      to directory baz

      Now whichever of the two checkouts is listed first in the job will succeed, and
      the second will fail. The error for the second checkout is:

      Checking out https://foo.com/project/baz

      ERROR: Failed to check out https://foo.com/project/baz
      org.tmatesoft.svn.core.SVNCancelException: svn: authentication cancelled
      at
      org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:60)
      at
      org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)
      at
      org.tmatesoft.svn.core.internal.io.dav.DAVUtil.findStartingProperties(DAVUtil.java:126)
      at
      org.tmatesoft.svn.core.internal.io.dav.DAVUtil.getBaselineProperties(DAVUtil.java:216)
      at org.tmatesoft.svn.core.internal.io.dav.DAVUtil.getBaselineInfo(DAVUtil.java:174)
      at
      org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getLatestRevision(DAVRepository.java:182)
      at
      org.tmatesoft.svn.core.wc.SVNBasicClient.getRevisionNumber(SVNBasicClient.java:482)
      at org.tmatesoft.svn.core.wc.SVNBasicClient.getLocations(SVNBasicClient.java:851)
      at
      org.tmatesoft.svn.core.wc.SVNBasicClient.createRepository(SVNBasicClient.java:534)
      at org.tmatesoft.svn.core.wc.SVNUpdateClient.doCheckout(SVNUpdateClient.java:893)
      at org.tmatesoft.svn.core.wc.SVNUpdateClient.doCheckout(SVNUpdateClient.java:791)
      at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:607)
      at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:533)
      at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2014)
      at hudson.remoting.UserRequest.perform(UserRequest.java:103)
      at hudson.remoting.UserRequest.perform(UserRequest.java:47)
      at hudson.remoting.Request$2.run(Request.java:236)
      at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
      at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
      at java.util.concurrent.FutureTask.run(Unknown Source)
      at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
      at java.lang.Thread.run(Unknown Source)

      in the job config.xml file it records only one authToken. Not sure how it
      decides that the two paths should have the same username/password.

      Running the subversion plugin 1.4 built against 1.310 from here does not change
      the behavior:

      https://hudson.dev.java.net/servlets/ProjectDocumentList?folderID=11503&expandFolder=11503&folderID=5818

      This 1.313 change looks fishy to me:

      https://hudson.dev.java.net/issues/show_bug.cgi?id=2909

      Could this behavior also be affected by the root cause?

      https://hudson.dev.java.net/issues/show_bug.cgi?id=4018 (this symptom is about
      tagging)

            Unassigned Unassigned
            jehenrik jehenrik
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: