[JIRA] [workflow-plugin] (JENKINS-26659) file permissions aren't protected after archive/unarchive
Title: Message Title Jesse Glick resolved as Won't Fix unarchive has been deprecated in 1.10 in favor of stash/unstash, which internally use a .tar.gz file that ought to preserve file atttributes. Jenkins / JENKINS-26659 file permissions aren't protected after archive/unarchive Change By: Jesse Glick Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26659) file permissions aren't protected after archive/unarchive
Jesse Glick commented on JENKINS-26659 file permissions arent protected after archive/unarchive Yes, of course it is best to avoid relying on it (and for example tar up any files locally whose exact permissions you want to preserve), but insofar as the archive step (using StandardArtifactManager) preserves permissions and symlinks, unarchive should as well. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26659) file permissions aren't protected after archive/unarchive
Daniel Beck commented on JENKINS-26659 file permissions arent protected after archive/unarchive Assuming workflow archives on the master (like regular Archive Artifacts) I wouldn't rely on this anyway might be a Windows machine which would lose that information anyway. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26659) file permissions aren't protected after archive/unarchive
Jesse Glick commented on JENKINS-26659 file permissions arent protected after archive/unarchive I think this belongs here. UnarchiveStep is rather simplistic and makes no attempt to handle file permissions, symlinks, or any other subtleties. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26659) file permissions aren't protected after archive/unarchive
Timur Batyrshin
created JENKINS-26659
file permissions arent protected after archive/unarchive
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
workflow-plugin
Created:
28/Jan/15 9:38 AM
Description:
If file has executable bit set and is archived then after unarchiving the executable bit is missing.
Example flow:
node {
sh "touch test.sh chmod 0755 test.sh"
sh "ls -l test.sh"
archive "test.sh"
unarchive mapping: ["test.sh": "restore.sh"]
sh "ls -lR"
}
Output:
Started by user Timur
Running: Allocate node : Start
Running on master in /mnt1/jenkins/jobs/test-flow/workspace
Running: Allocate node : Body : Start
Running: Shell Script
[workspace] Running shell script
+ touch test.sh
+ chmod 0755 test.sh
Running: Shell Script
[workspace] Running shell script
+ ls -l test.sh
-rwxr-xr-x 1 jenkins jenkins 0 Jan 28 09:34 test.sh
Running: Archive Artifacts
Running: Copy archived artifacts into the workspace
Running: Shell Script
[workspace] Running shell script
+ ls -lR
.:
total 0
-rw-r--r-- 1 jenkins jenkins 0 Jan 28 09:34 restore.sh
-rwxr-xr-x 1 jenkins jenkins 0 Jan 28 09:34 test.sh
Running: Allocate node : Body : End
Running: Allocate node : End
Running: End of Workflow
Finished: SUCCESS
It probably relates to some other plugin but not to workflow-plugin but I don't know how to create reproduceable case without using workflow-plugin.
Project:
Jenkins
Priority:
Major
Reporter:
Timur Batyrshin
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
