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

When workspace is cloned, symlinks are replaced with copies of the files they point to

      When a project uses the "clone workspace for SCM" feature to grab a workspace from another project, somewhere in that process all symlinks in the original workspace are replaced with COPIES of the files they are supposed to point to. These copies are then afflicted with JENKINS-8677, where their exec permissions are wiped out. I'm pretty sure this is related to the clone workspace plugin. When I look at the workspace the files are coming FROM, everything is fine. Then the workspace they end up in, in the job that clones them, shows this symlink issue.

          [JENKINS-9118] When workspace is cloned, symlinks are replaced with copies of the files they point to

          Owen Mehegan created issue -
          Owen Mehegan made changes -
          Link New: This issue is related to JENKINS-8677 [ JENKINS-8677 ]
          SCM/JIRA link daemon made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          kutzi made changes -
          Link New: This issue is related to JENKINS-13614 [ JENKINS-13614 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 139274 ] New: JNJira + In-Review [ 188423 ]
          Jenkins IRC Bot made changes -
          Component/s New: clone-workspace-scm-plugin [ 16060 ]
          Component/s Original: clone-workspace-plugin [ 15700 ]

            abayer Andrew Bayer
            owenmehegan Owen Mehegan
            Votes:
            2 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: