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

Jenkins 1.509 has different behaviour with symlink handling of e.g. lastSuccessful

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Minor Minor
    • core
    • None

      I upgraded a system to Jenkins v1.509 and noticed a custom script breaks now which used to work fine. The reason seems to be a change which seems to have been introduced somewhere around v1.509 if I'm not mistaken.

      Old behaviour:

      1. ls -la /var/lib/jenkins/jobs/foo/lastSuccessful
        lrwxrwxrwx 1 jenkins nogroup 26 Feb 1 22:00 /var/lib/jenkins/jobs/foo/lastSuccessful -> builds/2013-02-01_22-00-34/

      New behaviour:

      1. ls -la /var/lib/jenkins/jobs/foo/lastSuccessful
        lrwxrwxrwx 1 jenkins nogroup 26 Apr 3 07:02 /var/lib/jenkins/jobs/foo/lastSuccessful -> builds/lastSuccessfulBuild/

      People using the target's name of the symlink (like "2013-02-01_22-00-34" in my example) inside scripts for further processing might have broken scripts due to that change.

      Could someone please confirm this change and the reason for that change?

          [JENKINS-17449] Jenkins 1.509 has different behaviour with symlink handling of e.g. lastSuccessful

          Michael Prokop created issue -
          kutzi made changes -
          Link New: This issue is related to JENKINS-16089 [ JENKINS-16089 ]
          kutzi made changes -
          Priority Original: Major [ 3 ] New: Minor [ 4 ]
          kutzi made changes -
          Resolution New: Not A Defect [ 7 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 148624 ] New: JNJira + In-Review [ 192804 ]

            Unassigned Unassigned
            mika Michael Prokop
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: