Open timja opened 9 years ago
If I manually "zip -r
.zip " on the slave, and then unzip everything is fine, so it has something to do with how Jenkins is creating the zip file.
Build artifacts are stored on the master.
Fair enough, but it's the same problem:
-bash-4.1$ pwd /disk01/jenkins/jobs/sast_product_linux64/lastSuccessful/archive/dist/bin -bash-4.1$ 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
Interesting.
Possible first version to behave like this could be 1.532 (for JENKINS-17236).
Obvious workaround would be to tar things to be sure all metadata and types (Jenkins also does not archive symlinks properly in all cases) are retained.
We considered the tar approach, but then you lose fingerprinting.
Fingerprinter Plugin allows fingerprinting arbitrary files. It's a bit redundant but may work for you.
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:
When I download all artifacts as a zip, this is what is in the directory after extraction:
If I manually "zip -r
Originally reported by davidsj2, imported from: (all files in zip) link generates a zip archive that doesn't maintain permissions