[JIRA] (JENKINS-43540) builds/lastSuccessfulBuild symlink is not created

2 views
Skip to first unread message

i_kit@cloud.upwork.com (JIRA)

unread,
Sep 23, 2018, 4:39:02 PM9/23/18
to jenkinsc...@googlegroups.com
Ivan Kit commented on Bug JENKINS-43540
 
Re: builds/lastSuccessfulBuild symlink is not created

Have same issues on version: Jenkins ver. 2.142 

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

floody@inf.elte.hu (JIRA)

unread,
Dec 26, 2018, 4:09:02 AM12/26/18
to jenkinsc...@googlegroups.com

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?

daniel.jeznach@imgtec.com (JIRA)

unread,
Mar 29, 2019, 5:54:03 AM3/29/19
to jenkinsc...@googlegroups.com

I have similiar issue with no lastCompletedBuild, looks related.

jglick@cloudbees.com (JIRA)

unread,
Aug 21, 2019, 9:45:01 AM8/21/19
to jenkinsc...@googlegroups.com

As of JENKINS-37862 Jenkins does not create build symlinks any more, so this may be obsolete.

Reply all
Reply to author
Forward
0 new messages