Artifact permissions lost after fetch

[Rabea]

I have an issue when I publish my artifact (as a build artifact type) and then fetch 
files permissions are not preserved 
my artifact is as follows:
I do git clone, then npm install and I publish the whole folder (my repo after npm install)
and after fetching the artifact , I can see that the binaries under node_modules/.bin 
don't have execute permission. (That is just one example)

I have see open git issue from 2015 but it did not get resolved.

https://github.com/gocd/gocd/issues/464

is there a solution or a workaround?

[Chad Wilson]

The GitHub issue refers to the workarounds - one for your case might be to tar up the files yourself and publish a file artifact for the tarball archive rather than a directory artifact, then untar it after fetch.

-Chad

--
You received this message because you are subscribed to the Google Groups "go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email to go-cd+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/113bb637-2855-4e24-9dac-309b997085e8n%40googlegroups.com.

[Rabea]

Thanks , I was hoping that I won't have to tar an untar manually, but it is a good enough solution for now, I hope there will be a built in solution in newer releases.

[Chad Wilson]

From a theoretical perspective, if you don't have a need for pipelines to retrieve individual files and folders from within, it is more efficient and arguably better practice (immutability of the collection) to store a single artifact rather than artifacting a collection of files that can be individually referenced and retrieved.

To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/94cdd964-7b73-4dff-a5f2-4f6a77d45ddfn%40googlegroups.com.