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

Build Pipeline plugin loses track of upstream build when retrying of a failed build

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • build-pipeline-plugin
    • None
    • Jenkins 1.594
      Build-pipeline-plugin 1.4.7

      Given:

      • A pipeline exists with multiple jobs chained
      • Pipeline is triggered
      • A job in the middle of pipeline fails

      When:

      • Retry of the failed job is clicked

      Then:

      • The new retried job is run and build is started
      • The new retried job has no Upstream link anymore in the "build.xml" visible, the failed build has:
        " <hudson.model.Cause_-UpstreamCause>
        <upstreamProject"
      • The pipeline view thus is showing only the first failed build, not the successful one -> Unable to proceed in pipeline

          [JENKINS-28478] Build Pipeline plugin loses track of upstream build when retrying of a failed build

          Cesar G added a comment - - edited

          any updates? I'm having the same issue. I saw also that build-card is not updating the job number even when after a retry the job ends successfully (it changes to green state but after refresh back to red and old build number).

          Cesar G added a comment - - edited any updates? I'm having the same issue. I saw also that build-card is not updating the job number even when after a retry the job ends successfully (it changes to green state but after refresh back to red and old build number).

          John Martel added a comment -

          Got the same issue here. Build number is not updated in the pipeline view for the "failed-then-successful" job and the backgrouond stays red.

          John Martel added a comment - Got the same issue here. Build number is not updated in the pipeline view for the "failed-then-successful" job and the backgrouond stays red.

          Ville Hartikainen added a comment -

          Still open, hoping for to get some time and study how the plugin is built. There is a workaround though:

          1. Delete the failed task
          2. Click on "run"

          Ville Hartikainen added a comment - Still open, hoping for to get some time and study how the plugin is built. There is a workaround though: Delete the failed task Click on "run"

          Niraj Khanal added a comment -

          Could you please be a little more specific about the workaround? I am unable to run the pipeline and not sure what to delete. Thank You.

          Niraj Khanal added a comment - Could you please be a little more specific about the workaround? I am unable to run the pipeline and not sure what to delete. Thank You.

          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
            vphartik Ville Hartikainen
            Votes:
            6 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: