• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • core
    • Jenkins 2.46.2
      openjdk 1.8.0
      ubnutu 16.04 lts
    • 2.198

      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?

          [JENKINS-56809] No lastCompletedBuild symlink

          Daniel Jeznach created issue -
          Daniel Jeznach made changes -
          Labels New: symlink
          Daniel Jeznach made changes -
          Description Original: 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?
          New: 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 made changes -
          Description Original: 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?
          New: 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 made changes -
          Description Original: 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?
          New: 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 made changes -
          Description Original: 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?
          New: 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 made changes -
          Description Original: 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?
          New: 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?
          Jesse Glick made changes -
          Link New: This issue relates to JENKINS-37862 [ JENKINS-37862 ]
          Jesse Glick made changes -
          Resolution New: Won't Fix [ 2 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          Daniel Jeznach made changes -
          Resolution Original: Won't Fix [ 2 ]
          Status Original: Resolved [ 5 ] New: In Review [ 10005 ]
          Jesse Glick made changes -
          Status Original: In Review [ 10005 ] New: In Progress [ 3 ]

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

              Created:
              Updated:
              Resolved: