• 2.1.1

      Something changed in the naming of the workspace folders on the Jenkins Master node. Previously, the name the was suffixed with a long random (names are examples only, the exact length is different):

      MyProjectA1_MyBranch-ZOBMWQA2JSVUZRAPJAQ3NT3TSBIUQOS26N5CF3XJB@libs
      MyProjectA1_MyBranch-ZOBMWQA2JSVUZRAPJAQ3NT3TSBIUQOS26N5CF3XJB@script
      MyVeryLongBranchName-NHOUUZPM5MARPAN7OGASNLPNCKRLL26RQKEZIEEKC@libs
      MyVeryLongBranchName-NHOUUZPM5MARPAN7OGASNLPNCKRLL26RQKEZIEEKC@script
      MyVeryLongBranchName-TN6NSHXVGMKRKUOVV7CKNODZOK3JSHI4CQYCOR4E6@libs
      MyVeryLongBranchName-TN6NSHXVGMKRKUOVV7CKNODZOK3JSHI4CQYCOR4E6@script
      

      However now, this suffix seems to be removed, causing name clashes when different repositories have long but identical branch names:

      MyProjectA1_MyBranch@libs
      MyProjectA1_MyBranch@script
      MyVeryLongBranchName@libs    <<-\
      MyVeryLongBranchName@script     |   <<-\
      MyVeryLongBranchName@libs    <<-/      |
      MyVeryLongBranchName@script         <<-/
      

      The last two repositories are unrelated but map to the same directory, causing "unrelated repository" errors during checkout.

          [JENKINS-54640] Workspace folders are not unique

          kpop created issue -
          kpop made changes -
          Environment Original: Jenkins 2.151 New: Jenkins 2.151
          pipeline 2.5
          pipeline-multibranch 2.20
          kpop made changes -
          Component/s New: pipeline-multibranch-defaults-plugin [ 21926 ]
          kpop made changes -
          Link New: This issue relates to JENKINS-38706 [ JENKINS-38706 ]
          Øyvind R made changes -
          Link New: This issue relates to JENKINS-54654 [ JENKINS-54654 ]
          Jesse Glick made changes -
          Component/s New: branch-api-plugin [ 18621 ]
          Component/s Original: pipeline [ 21692 ]
          Component/s Original: pipeline-multibranch-defaults-plugin [ 21926 ]
          Jesse Glick made changes -
          Link New: This issue relates to JENKINS-2111 [ JENKINS-2111 ]

          Jesse Glick added a comment -

          The fix of JENKINS-2111 removed the long hash from workspace names. However, it introduced a workspaces.txt file which tracks which directory is used for which project. Evidently this is not working in your case. Please provide complete steps to reproduce the problem from scratch, or at a minimum run this build (Plugin Manager » Advanced to upload) and create a custom logger on jenkins.branch.WorkspaceLocatorImpl to assist in remote diagnosis.

          Jesse Glick added a comment - The fix of JENKINS-2111 removed the long hash from workspace names. However, it introduced a workspaces.txt file which tracks which directory is used for which project. Evidently this is not working in your case. Please provide complete steps to reproduce the problem from scratch, or at a minimum run this build ( Plugin Manager » Advanced to upload) and create a custom logger on jenkins.branch.WorkspaceLocatorImpl to assist in remote diagnosis.

          Jesse Glick added a comment -

          kpop I added some more information on diagnostics to JENKINS-54654.

          Jesse Glick added a comment - kpop I added some more information on diagnostics to JENKINS-54654 .

          kpop added a comment -

          jglick, thank you for the custom build. I've installed it and enabled the logging. I'll will report back if I can reproduce the issue.

          kpop added a comment - jglick , thank you for the custom build. I've installed it and enabled the logging. I'll will report back if I can reproduce the issue.

            jglick Jesse Glick
            kpop kpop
            Votes:
            1 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: