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


    • Similar Issues:


      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.


          Issue Links


            owenmehegan Owen Mehegan created issue -
            owenmehegan Owen Mehegan made changes -
            Field Original Value New Value
            Link This issue is related to JENKINS-8677 [ JENKINS-8677 ]
            scm_issue_link SCM/JIRA link daemon made changes -
            Status Open [ 1 ] Resolved [ 5 ]
            Resolution Fixed [ 1 ]
            kutzi kutzi made changes -
            Link This issue is related to JENKINS-13614 [ JENKINS-13614 ]
            rtyler R. Tyler Croy made changes -
            Workflow JNJira [ 139274 ] JNJira + In-Review [ 188423 ]


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


                • Created: