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

No lastCompletedBuild symlink

    XMLWordPrintable

    Details

    • Similar Issues:
    • Released As:
      2.198

      Description

      I maintain few jenkinses, various versions (2.x). Some of jobs on them publish artifacts even when build result is failure. Using jenkins UI I can access artifacts via http url

      JENKINS_URL/job/jobname/lastCompletedBuild/artifact/file.ext

      But I need to access this artifact directly from filesystem where artifacts are stored, in my case it is custom path:

      /mnt/jenkins/builds/jobname/lastCompletedBuild/archive/file.ext

      On disk, lastCompletedBuild symlink is not created. I still can access the file, but I have to know build number. The same is for lastBuild. To sum up: it works for lastCompletedBuild, lastUnstableBuild, lastFailedBuild, lastUnsuccessfulBuild. All shorthand urls from job page have their respective symlinks created, except lastCompletedBuild.

      Is it intentional?

        Attachments

          Issue Links

            Activity

            daniel_jeznach_img Daniel Jeznach created issue -
            daniel_jeznach_img Daniel Jeznach made changes -
            Field Original Value New Value
            Labels symlink
            daniel_jeznach_img Daniel Jeznach made changes -
            Description I maintain few jenkinses, various versions (2.x). Some of them publish artifacts even when build result is failure.

            Using jenkins UI I can access artifacts via http url JENKINS_URL/job/jobname/lastCompletedBuild/artifact/file.ext

            But I need to access this artifact directly from filesystem where artifacts are stored, in my case it is custom path:

            /mnt/jenkins/builds/jobname/lastCompletedBuild/archive/file.ext

            but lastCompletedBuild symlink is not created. I still can access the file, but I have to know build number. The same is for lastBuild.

            It works for lastCompletedBuild, lastUnstableBuild, lastFailedBuild, lastUnsuccessfulBuild.

            All short url from job page have their respective symlinks except lastCompletedBuild.

            Is it intentional?
            I maintain few jenkinses, various versions (2.x). Some of jobs on them publish artifacts even when build result is failure.

            Using jenkins UI I can access artifacts via http url JENKINS_URL/job/jobname/lastCompletedBuild/artifact/file.ext

            But I need to access this artifact directly from filesystem where artifacts are stored, in my case it is custom path:

            /mnt/jenkins/builds/jobname/lastCompletedBuild/archive/file.ext

            but lastCompletedBuild symlink is not created. I still can access the file, but I have to know build number. The same is for lastBuild.

            It works for lastCompletedBuild, lastUnstableBuild, lastFailedBuild, lastUnsuccessfulBuild.

            All short url from job page have their respective symlinks except lastCompletedBuild.

            Is it intentional?
            daniel_jeznach_img Daniel Jeznach made changes -
            Description I maintain few jenkinses, various versions (2.x). Some of jobs on them publish artifacts even when build result is failure.

            Using jenkins UI I can access artifacts via http url JENKINS_URL/job/jobname/lastCompletedBuild/artifact/file.ext

            But I need to access this artifact directly from filesystem where artifacts are stored, in my case it is custom path:

            /mnt/jenkins/builds/jobname/lastCompletedBuild/archive/file.ext

            but lastCompletedBuild symlink is not created. I still can access the file, but I have to know build number. The same is for lastBuild.

            It works for lastCompletedBuild, lastUnstableBuild, lastFailedBuild, lastUnsuccessfulBuild.

            All short url from job page have their respective symlinks except lastCompletedBuild.

            Is it intentional?
            I maintain few jenkinses, various versions (2.x). Some of jobs on them publish artifacts even when build result is failure.

            Using jenkins UI I can access artifacts via http url JENKINS_URL/job/jobname/lastCompletedBuild/artifact/file.ext

            But I need to access this artifact directly from filesystem where artifacts are stored, in my case it is custom path:

            {{/mnt/jenkins/builds/jobname/lastCompletedBuild/archive/file.ext}}

            but lastCompletedBuild symlink is not created. I still can access the file, but I have to know build number. The same is for lastBuild.

            It works for lastCompletedBuild, lastUnstableBuild, lastFailedBuild, lastUnsuccessfulBuild. All shorthand urls from job page have their respective symlinks created, except lastCompletedBuild.

            Is it intentional?
            daniel_jeznach_img Daniel Jeznach made changes -
            Description I maintain few jenkinses, various versions (2.x). Some of jobs on them publish artifacts even when build result is failure.

            Using jenkins UI I can access artifacts via http url JENKINS_URL/job/jobname/lastCompletedBuild/artifact/file.ext

            But I need to access this artifact directly from filesystem where artifacts are stored, in my case it is custom path:

            {{/mnt/jenkins/builds/jobname/lastCompletedBuild/archive/file.ext}}

            but lastCompletedBuild symlink is not created. I still can access the file, but I have to know build number. The same is for lastBuild.

            It works for lastCompletedBuild, lastUnstableBuild, lastFailedBuild, lastUnsuccessfulBuild. All shorthand urls from job page have their respective symlinks created, except lastCompletedBuild.

            Is it intentional?
            I maintain few jenkinses, various versions (2.x). Some of jobs on them publish artifacts even when build result is failure. Using jenkins UI I can access artifacts via http url

            {{JENKINS_URL/job/jobname/lastCompletedBuild/artifact/file.ext }}

            But I need to access this artifact directly from filesystem where artifacts are stored, in my case it is custom path:

            {{/mnt/jenkins/builds/jobname/lastCompletedBuild/archive/file.ext}}

            On disk, lastCompletedBuild symlink is not created. I still can access the file, but I have to know build number. The same is for lastBuild. To sum up: it works for lastCompletedBuild, lastUnstableBuild, lastFailedBuild, lastUnsuccessfulBuild. All shorthand urls from job page have their respective symlinks created, except lastCompletedBuild.

            Is it intentional?
            daniel_jeznach_img Daniel Jeznach made changes -
            Description I maintain few jenkinses, various versions (2.x). Some of jobs on them publish artifacts even when build result is failure. Using jenkins UI I can access artifacts via http url

            {{JENKINS_URL/job/jobname/lastCompletedBuild/artifact/file.ext }}

            But I need to access this artifact directly from filesystem where artifacts are stored, in my case it is custom path:

            {{/mnt/jenkins/builds/jobname/lastCompletedBuild/archive/file.ext}}

            On disk, lastCompletedBuild symlink is not created. I still can access the file, but I have to know build number. The same is for lastBuild. To sum up: it works for lastCompletedBuild, lastUnstableBuild, lastFailedBuild, lastUnsuccessfulBuild. All shorthand urls from job page have their respective symlinks created, except lastCompletedBuild.

            Is it intentional?
            I maintain few jenkinses, various versions (2.x). Some of jobs on them publish artifacts even when build result is failure. Using jenkins UI I can access artifacts via http url

            JENKINS_URL/job/jobname/lastCompletedBuild/artifact/file.ext

            But I need to access this artifact directly from filesystem where artifacts are stored, in my case it is custom path:

            {{/mnt/jenkins/builds/jobname/lastCompletedBuild/archive/file.ext}}

            On disk, lastCompletedBuild symlink is not created. I still can access the file, but I have to know build number. The same is for lastBuild. To sum up: it works for lastCompletedBuild, lastUnstableBuild, lastFailedBuild, lastUnsuccessfulBuild. All shorthand urls from job page have their respective symlinks created, except lastCompletedBuild.

            Is it intentional?
            daniel_jeznach_img Daniel Jeznach made changes -
            Description I maintain few jenkinses, various versions (2.x). Some of jobs on them publish artifacts even when build result is failure. Using jenkins UI I can access artifacts via http url

            JENKINS_URL/job/jobname/lastCompletedBuild/artifact/file.ext

            But I need to access this artifact directly from filesystem where artifacts are stored, in my case it is custom path:

            {{/mnt/jenkins/builds/jobname/lastCompletedBuild/archive/file.ext}}

            On disk, lastCompletedBuild symlink is not created. I still can access the file, but I have to know build number. The same is for lastBuild. To sum up: it works for lastCompletedBuild, lastUnstableBuild, lastFailedBuild, lastUnsuccessfulBuild. All shorthand urls from job page have their respective symlinks created, except lastCompletedBuild.

            Is it intentional?
            I maintain few jenkinses, various versions (2.x). Some of jobs on them publish artifacts even when build result is failure. Using jenkins UI I can access artifacts via http url

            {{JENKINS_URL/job/jobname/lastCompletedBuild/artifact/file.ext}}

            But I need to access this artifact directly from filesystem where artifacts are stored, in my case it is custom path:

            {{/mnt/jenkins/builds/jobname/lastCompletedBuild/archive/file.ext}}

            On disk, lastCompletedBuild symlink is not created. I still can access the file, but I have to know build number. The same is for lastBuild. To sum up: it works for lastCompletedBuild, lastUnstableBuild, lastFailedBuild, lastUnsuccessfulBuild. All shorthand urls from job page have their respective symlinks created, except lastCompletedBuild.

            Is it intentional?
            jglick Jesse Glick made changes -
            Link This issue relates to JENKINS-37862 [ JENKINS-37862 ]
            jglick Jesse Glick made changes -
            Resolution Won't Fix [ 2 ]
            Status Open [ 1 ] Resolved [ 5 ]
            daniel_jeznach_img Daniel Jeznach made changes -
            Resolution Won't Fix [ 2 ]
            Status Resolved [ 5 ] In Review [ 10005 ]
            jglick Jesse Glick made changes -
            Status In Review [ 10005 ] In Progress [ 3 ]
            jglick Jesse Glick made changes -
            Status In Progress [ 3 ] Open [ 1 ]
            jglick Jesse Glick made changes -
            Link This issue relates to JENKINS-26270 [ JENKINS-26270 ]
            jglick Jesse Glick made changes -
            Assignee Jesse Glick [ jglick ]
            jglick Jesse Glick made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            jglick Jesse Glick made changes -
            Remote Link This issue links to "jenkins #4228 (Web Link)" [ 23722 ]
            jglick Jesse Glick made changes -
            Status In Progress [ 3 ] In Review [ 10005 ]
            jglick Jesse Glick made changes -
            Released As 2.198
            Resolution Fixed [ 1 ]
            Status In Review [ 10005 ] Fixed but Unreleased [ 10203 ]
            danielbeck Daniel Beck made changes -
            Status Fixed but Unreleased [ 10203 ] Closed [ 6 ]
            danielbeck Daniel Beck made changes -
            Labels symlink lts-candidate symlink
            olivergondza Oliver Gond┼ża made changes -
            Labels lts-candidate symlink 2.190.3-fixed symlink

              People

              Assignee:
              jglick Jesse Glick
              Reporter:
              daniel_jeznach_img Daniel Jeznach
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: