[JIRA] (JENKINS-54998) Stash and archive should refuse symlinks

[jglick@cloudbees.com (JIRA)]

Jesse Glick updated an issue

Jenkins / JENKINS-54998 Stash and archive should refuse symlinks Change By: Jesse Glick Summary: Stash and archive should resolve refuse symlinks Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[oesolutions@gmail.com (JIRA)]

Chris Dore commented on JENKINS-54998

Re: Stash and archive should refuse symlinks Jesse Glick why should a symlink be an error? Since symlinks are not preserved, we abandoned using stash and instead we are now allocating a node for the entire pipeline, even when that node could be released back to the pool during certain stages. I would love to revisit our workaround and improve node utilization, having stash handle symlinks would make this very easy. Are there other alternative ideas to allow a pipeline to save state containing symlinks across stages on different nodes/workspaces?

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

[jglick@cloudbees.com (JIRA)]

Jesse Glick commented on JENKINS-54998

Re: Stash and archive should refuse symlinks

Use tar and decide in your script which options to pass to get the desired behavior: preserving symlinks, preserving other special files, preserving owner, preserving mode, etc.

Add Comment