[JIRA] (JENKINS-43407) hudson.Util.noSymLink option not respected

1 view
Skip to first unread message

floody@inf.elte.hu (JIRA)

unread,
Dec 24, 2018, 4:43:04 AM12/24/18
to jenkinsc...@googlegroups.com
Andor Herendi commented on Bug JENKINS-43407
 
Re: hudson.Util.noSymLink option not respected

Hello Guys!

Is this still a thing? I've checked the codebase and they altered the behavior in this commit.

For me, it seems the noSymLink and symlinkEscapeHatch environment variables are no longer in use or not making any difference for the code. By default, the code tries to create the links and if it isn't supported by the filesystem, then it catches the exception and logs its content into the log files.

If my assumptions are correct and noSymLink and symlinkEscapeHatch doesn't alters the behavior elsewhere, then we should remove these two variables from this page, because these are no longer supported or used.

I also planning to move Jenkins' home to such a filesystem (Azure Files) where the symlinks are not supported. Did you saw any side-effects while using Jenkins?

 

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

jglick@cloudbees.com (JIRA)

unread,
Aug 21, 2019, 9:46:07 AM8/21/19
to jenkinsc...@googlegroups.com
Jesse Glick resolved as Won't Fix
 

As of JENKINS-37862 Jenkins does not use build symlinks by default, so this should not be an issue.

Jenkins / Bug JENKINS-43407
hudson.Util.noSymLink option not respected
Change By: Jesse Glick
Status: Open Resolved
Resolution: Won't Fix
Reply all
Reply to author
Forward
0 new messages