-
Bug
-
Resolution: Fixed
-
Major
-
None
This is definitely true for zips, and I think it's true for tars as well - when we're creating tarballs and zipfiles, we're not actually looking at the permissions/unix mode on the files and directories going into them. As a result, the tars/zips we've created have no useful permissions set. This is particularly annoying with the clone workspace SCM plugin, where files may need to be executable for the downstream to work properly.
- is blocking
-
JENKINS-2572 file permissions are lost
-
- Resolved
-
-
JENKINS-8677 When workspace is cloned, exec permissions on files are wiped out
-
- Resolved
-
-
JENKINS-9741 Copy artifact loses file permissions
-
- Closed
-
-
JENKINS-8140 CopyArtifact plugin should preserve executable bits
-
- Closed
-
- is related to
-
JENKINS-13128 Artifacts Permissions Stripped
-
- Resolved
-
-
JENKINS-9577 Clone workspace does not preserve permissions
-
- Resolved
-
Code changed in jenkins
User: Andrew Bayer
Path:
core/src/main/java/hudson/util/io/Archiver.java
core/src/main/java/hudson/util/io/TarArchiver.java
core/src/main/java/hudson/util/io/ZipArchiver.java
http://jenkins-ci.org/commit/jenkins/00485b3188236f17b4962790945ae3218de98d09
Log:
[FIXED JENKINS-9397] Added convenience method to hudson.util.io.Archiver to get the Unix mode (if appropriate) for a file, and modified TarArchiver and ZipArchiver to utilise this to get and set the Unix mode for files whent they're being archived.