Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-43540

builds/lastSuccessfulBuild symlink is not created

    XMLWordPrintable

Details

    Description

      Build does not create the respective lastSuccess and lastStable symlinks i the build folder:

      drwxr-xr-x. 3 jenkins jenkins 64 Apr 12 13:07 builds
      lrwxrwxrwx. 1 jenkins jenkins 22 Apr 12 13:05 lastStable -> builds/lastStableBuild
      lrwxrwxrwx. 1 jenkins jenkins 26 Apr 12 13:05 lastSuccessful -> builds/lastSuccessfulBuild
      rw-rr-. 1 jenkins jenkins 2 Apr 12 13:05 nextBuildNumber
      drwxr-xr-x. 26 jenkins jenkins 4.0K Apr 12 13:06 workspace

      drwxr-xr-x. 3 jenkins jenkins 64 Apr 12 13:07 .
      drwxr-xr-x. 4 jenkins jenkins 95 Apr 12 13:05 ..
      drwxr-xr-x. 3 jenkins jenkins 92 Apr 12 13:07 1
      lrwxrwxrwx. 1 jenkins jenkins 1 Apr 12 13:07 lastFailedBuild -> 1
      lrwxrwxrwx. 1 jenkins jenkins 1 Apr 12 13:07 lastUnsuccessfulBuild -> 1

       

      Already added the 

      JENKINS_JAVA_OPTIONS="-Djava.awt.headless=true -Dhudson.Util.symlinkEscapeHatch=true"

      to /etc/sysconfig/jenkins file and restartet

       

      Also purged build history and deleted the respective job folder

      Attachments

        Issue Links

          Activity

            jglick Jesse Glick added a comment -

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

            jglick Jesse Glick added a comment - As of JENKINS-37862 Jenkins does not create build symlinks any more, so this may be obsolete.

            I have similiar issue with no lastCompletedBuild, looks related.

            daniel_jeznach_img Daniel Jeznach added a comment - I have similiar issue with no lastCompletedBuild, looks related.
            floody Andor Herendi added a comment -

            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?

            floody Andor Herendi added a comment - 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?
            mentat Ivan Kit added a comment -

            Have same issues on version: Jenkins ver. 2.142 

            mentat Ivan Kit added a comment - Have same issues on version:  Jenkins ver. 2.142  

            People

              vjuranek vjuranek
              mruepp Michael Ruepp
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated: