Change By: Josh Davidson (10/Feb/15 6:20 PM)
Description: When using a the option to download all artifacts as a zip on a Linux job, the resulting archive doesn't maintain the permissions of the original file.  A couple years ago, this used to work.  It first broke for us when we upgrade to a 1.5x LTS release.  We've recently switched to latest (1.598) and it is still broke.

Here is an example from directory in a slave's workspace that is part of the archived artifacts:
{code}
ls -l | head -4
total 42288
-rwxr-xr-x 1 goesrjen goesrsw    74575 Feb 10 10:01 CreateSizes
-rwxr-xr-x 1 goesrjen goesrsw      832 Apr  2  2014 create-workspace
-rw-r--r-- 1 goesrjen goesrsw 25816831 Jan 26 20:19 GroundServiceApp.jar
{code}

When I download all artifacts as a zip, this is what is in the directory after extraction:
{code}
ls -l | head -4
total 42288
-rw-r--r-- 1 davidsj2 goesrsw    74575 Feb 10 10:01 CreateSizes
-rw-r--r-- 1 davidsj2 goesrsw      832 Apr  2  2014 create-workspace
-rw-r--r-- 1 davidsj2 goesrsw 25816831 Jan 26 20:19 GroundServiceApp.jar
{code}

If I manually "zip -r <dir>.zip <dir>" on the slave, and then unzip everything is fine, so it has something to do with how Jenkins is creating the zip file.
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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to