Details
-
Bug
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
Linux
Description
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.
Attachments
Issue Links
- is related to
-
JENKINS-8677 When workspace is cloned, exec permissions on files are wiped out
-
- Resolved
-
-
JENKINS-13614 archiving artefacts from remote MacOS X, IBM AIX slave fails
-
- Resolved
-
Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
changelog.html
core/src/main/java/hudson/FilePath.java
core/src/main/java/hudson/FileSystemProvisioner.java
http://jenkins-ci.org/commit/jenkins/2dd70965a781f3f8477ce06d1ecf61f6c3017ace
Log:
[FIXED JENKINS-9118]
WorkspaceSnapshot now uses the tar.gz format to handle symlinks
correctly.
Compare: https://github.com/jenkinsci/jenkins/compare/132f8b7...2dd7096