[JIRA] (JENKINS-43540) builds/lastSuccessfulBuild symlink is not created
Title: Message Title Jesse Glick commented on JENKINS-43540 Re: builds/lastSuccessfulBuild symlink is not created As of JENKINS-37862 Jenkins does not create build symlinks any more, so this may be obsolete. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.180856.1492003353000.6931.1566395100205%40Atlassian.JIRA.
[JIRA] (JENKINS-43540) builds/lastSuccessfulBuild symlink is not created
Title: Message Title Daniel Jeznach commented on JENKINS-43540 Re: builds/lastSuccessfulBuild symlink is not created I have similiar issue with no lastCompletedBuild, looks related. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43540) builds/lastSuccessfulBuild symlink is not created
Title: Message Title Andor Herendi commented on JENKINS-43540 Re: builds/lastSuccessfulBuild symlink is not created 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 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43540) builds/lastSuccessfulBuild symlink is not created
Title: Message Title Ivan Kit commented on JENKINS-43540 Re: builds/lastSuccessfulBuild symlink is not created Have same issues on version: Jenkins ver. 2.142 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
