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

Build Pipeline Plugin doesn't link the jobs to it's corresponding build number after successful re-build.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Blocker Blocker
    • build-pipeline-plugin
    • Jenkins: 1.609.1
      Build Pipeline Plugin Version: 1.4.7

      In addition to JENKINS-28478 ( where the pipeline shows failed even though the job is successful) , I am seeing that Build Pipeline when run from the middle of the pipeline doesn't seem to link the job to it's correct build number . However, if i run the new pipeline, the new job takes me directly to that exact build. For example, if I have a shell script running for pipeline #10's deploy QA job and it failed. Now I go back to the deploy QA job and change the configuration. If I come back to pipeline #10's deploy QA job and re-run it,it takes the new changes but the link on the build pipeline view takes me to the previous job ( the first job that was run through the pipeline). But, if I come back to the list of QA builds from outside of Build Pipeline view and check the first executed job, it is the recent one. Also on the Build pipeline view, the timestamp seems to be there from previous build even though the job is re-executed. It would be nice to update the timestamp with the most recent successful build that was re-executed rather than the one which was created when the job ran first. It would also be nice to modify it such that the link will take to the corresponding build rather than the first one. I can elaborate it more if needed. Thanks

        1. Capture.JPG
          Capture.JPG
          25 kB
        2. Capture1.JPG
          Capture1.JPG
          21 kB
        3. Capture3.JPG
          Capture3.JPG
          38 kB

          [JENKINS-32885] Build Pipeline Plugin doesn't link the jobs to it's corresponding build number after successful re-build.

          Niraj Khanal added a comment -

          This is a blocker issue for us at the moment because the specific build designated to go to production cannot move further down the pipeline when this build ( succeeds on retry) but fails to display it in the build-pipeline view. So even though the build is successful, the pipeline shows red and the next job in the pipeline doesn't have a trigger. If we try to run the build from the list, it loses all of it's parameters so we can't go that way either. The only way right now is to re-run the pipeline which will create another artifact with a different version and has to go through each environment once again which adds another complexity because now the build asset has a different version ( which is tied to the build number). Any suggestions or workaround until it's fixed is welcome. Thanks

          Niraj Khanal added a comment - This is a blocker issue for us at the moment because the specific build designated to go to production cannot move further down the pipeline when this build ( succeeds on retry) but fails to display it in the build-pipeline view. So even though the build is successful, the pipeline shows red and the next job in the pipeline doesn't have a trigger. If we try to run the build from the list, it loses all of it's parameters so we can't go that way either. The only way right now is to re-run the pipeline which will create another artifact with a different version and has to go through each environment once again which adds another complexity because now the build asset has a different version ( which is tied to the build number). Any suggestions or workaround until it's fixed is welcome. Thanks

          Dan Alvizu added a comment -

          This is fixed in 1.4.9

          Dan Alvizu added a comment - This is fixed in 1.4.9

            dalvizu Dan Alvizu
            n33rajkhanal Niraj Khanal
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: