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

Rerunning failed Delivery Pipeline stage doesn't enable/disable a manual trigger when using the Join plugin

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • join-plugin
    • None
    • Jenkins 1.609.1
      Delivery Pipeline plugin 0.9.4
      Join plugin 1.15

      If a jobA triggers two other jobs (jobB and jobC), this would show as a split in a delivery pipeline view. If I want jobD to run after jobB and jobC completed (merge in the flow), I'd need to configure the Join plugin on jobA and say "run jobD once all downstream jobs have completed".

      This works fine, but if say jobC failed and I rerun that stage in the delivery pipeline view, jobD doesn't get enabled. After testing it seems that whether jobD runs or not is determined by the initial assessment of the Join plugin. No matter what I rerun from the downstream jobs (jobB, jobC), jobD stays in its original state.

        1. 002-Join-plugin-fix-to-allow-retry-on-failure.patch
          6 kB
        2. 0001-Join-plugin-fix-to-allow-retry-on-failure.patch
          3 kB

          [JENKINS-29652] Rerunning failed Delivery Pipeline stage doesn't enable/disable a manual trigger when using the Join plugin

          kolos created issue -
          Patrik Boström made changes -
          Link New: This issue is duplicated by JENKINS-28979 [ JENKINS-28979 ]
          Patrik Boström made changes -
          Component/s Original: delivery-pipeline-plugin [ 18134 ]

          Patrik Boström added a comment -

          This is an issue for Join plugin.

          Patrik Boström added a comment - This is an issue for Join plugin.
          Patrik Boström made changes -
          Resolution New: Duplicate [ 3 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

          Patrik Boström added a comment -

          Looks like the issue is resolved in Join plugin 1.16.

          Patrik Boström added a comment - Looks like the issue is resolved in Join plugin 1.16.

          Jean-Frédéric added a comment -

          I can confirm this is not fixed with Join plugin 1.16 − whether one retries a failed job using Naginator or the Delivery pipeline trigger.

          In jobC, the logs say:
          [Join] Pending does not contain jobC

          Jean-Frédéric added a comment - I can confirm this is not fixed with Join plugin 1.16 − whether one retries a failed job using Naginator or the Delivery pipeline trigger. In jobC, the logs say: [Join] Pending does not contain jobC

          Jean-Frédéric added a comment -

          Reopening per above comment.

          Jean-Frédéric added a comment - Reopening per above comment.
          Jean-Frédéric made changes -
          Resolution Original: Duplicate [ 3 ]
          Status Original: Resolved [ 5 ] New: Reopened [ 4 ]

          Chris Engel added a comment -

          I can confirm I'm seeing the same issue with Join plugin 1.16

          Chris Engel added a comment - I can confirm I'm seeing the same issue with Join plugin 1.16

            Unassigned Unassigned
            kolos kolos
            Votes:
            2 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated: