[JIRA] (JENKINS-53238) After unshelving a build, symlinks are broken

[pibe...@gmail.com (JIRA)]

Title: Message Title

Pierre Beitz created an issue   Jenkins / JENKINS-53238 After unshelving a build, symlinks are broken Issue Type: Bug Assignee: Pierre Beitz Components: shelve-project-plugin Created: 2018-08-25 17:48 Environment: Any shelve plugin version Jenkins version >= 2.91 Priority: Critical Reporter: Pierre Beitz After unshelving a project, the builds start with a stack for each symlink that are created by Jenkins eg:   ln builds/lastSuccessfulBuild jenkins-home/jobs/freestyle/lastSuccessful failed java.nio.file.DirectoryNotEmptyException: jenkins-home/jobs/freestyle/lastSuccessful at sun.nio.fs.UnixFileSystemProvider.implDelete(UnixFileSystemProvider.java:242) at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(AbstractFileSystemProvider.java:108) at java.nio.file.Files.deleteIfExists(Files.java:1165) at hudson.Util.createSymlink(Util.java:1351) at hudson.model.Run.createSymlink(Run.java:1937) at hudson.model.Run.updateSymlinks(Run.java:1918) at hudson.model.Run.execute(Run.java:1796) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Or ln builds/lastStableBuild jenkins-home/jobs/freestyle/lastStable failed java.nio.file.DirectoryNotEmptyException: jenkins-home/jobs/freestyle/lastStable at sun.nio.fs.UnixFileSystemProvider.implDelete(UnixFileSystemProvider.java:242) at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(AbstractFileSystemProvider.java:108) at java.nio.file.Files.deleteIfExists(Files.java:1165) at hudson.Util.createSymlink(Util.java:1351) at hudson.model.Run.createSymlink(Run.java:1937) at hudson.model.Run.updateSymlinks(Run.java:1919) at hudson.model.Run.execute(Run.java:1796) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Explanation Issue is due to a behavior change in Jenkins Core 2.91 that outlines an old bug in core. See JENKINS-52781 for details.   Workaround Waiting for a fix for JENKINS-52781, one can clean up the executors with this script: dry run (make sure of what you delete): find ${JENKINS_HOME}/jobs/ -type d \( -name lastFailedBuild -o -name lastSuccessfulBuild -o -name lastUnsuccessfulBuild -o -name lastStableBuild -o -name lastUnstableBuild -o -name lastFailed -o -name lastSuccessful -o -name lastUnsuccessful -o -name lastStable -o -name lastUnstable \) delete the symlinks: find ${JENKINS_HOME}/jobs/ -type d \( -name lastFailedBuild -o -name lastSuccessfulBuild -o -name lastUnsuccessfulBuild -o -name lastStableBuild -o -name lastUnstableBuild -o -name lastFailed -o -name lastSuccessful -o -name lastUnsuccessful -o -name lastStable -o -name lastUnstable \) -exec rm -rfv "{}" \; 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.