[ 
https://issues.jenkins-ci.org/browse/JENKINS-9118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160103#comment-160103
 ] 

dogfood commented on JENKINS-9118:
----------------------------------

Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! 
[jenkins_main_trunk #1580|http://ci.jenkins-ci.org/job/jenkins_main_trunk/1580/]
     [JENKINS-9118] (Revision d184d53b24a3a4f1b420ca6dbdb4438f72f1547b)
[FIXED JENKINS-9118] (Revision 2dd70965a781f3f8477ce06d1ecf61f6c3017ace)

     Result = SUCCESS
Kohsuke Kawaguchi : 
[d184d53b24a3a4f1b420ca6dbdb4438f72f1547b|https://github.com/jenkinsci/jenkins/commit/d184d53b24a3a4f1b420ca6dbdb4438f72f1547b]
Files : 
* core/src/test/java/hudson/FilePathTest.java
* core/src/main/java/hudson/FilePath.java
* pom.xml
* changelog.html
* core/src/main/java/hudson/util/DirScanner.java
* core/src/main/java/hudson/Util.java

Kohsuke Kawaguchi : 
[2dd70965a781f3f8477ce06d1ecf61f6c3017ace|https://github.com/jenkinsci/jenkins/commit/2dd70965a781f3f8477ce06d1ecf61f6c3017ace]
Files : 
* core/src/main/java/hudson/FileSystemProvisioner.java
* changelog.html
* core/src/main/java/hudson/FilePath.java

                
> When workspace is cloned, symlinks are replaced with copies of the files they 
> point to
> --------------------------------------------------------------------------------------
>
>                 Key: JENKINS-9118
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-9118
>             Project: Jenkins
>          Issue Type: Bug
>          Components: clone-workspace
>    Affects Versions: current
>         Environment: Linux
>            Reporter: owenmehegan
>            Assignee: abayer
>
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to