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

Option "Restrict trigger to the most recent build" showing trigger for all successful builds not only the most recent

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • build-pipeline-plugin
    • None
    • CentOS, Jenkins 1.515

      I have set option "Restrict trigger to the most recent build" to "Yes".

      See attached screen dump.

      The "Memphis - Release" downstream from "Memphis - Dev #37" does not have a trigger - this works as expected since "Memphis - Dev #37" failed.

      The "Memphis - Release" downstream from "Memphis - Dev #36" does have a trigger - this works as expected since "Memphis - Dev #36" is the latest successful build.

      But, the "Memphis - Release" downstream from "Memphis - Dev #33, #34, #35" also have a trigger - this does not work as expected since "Restrict trigger to the most recent build" is set to "Yes". I would expect those not to have a trigger as they are not the latest successful build.

          [JENKINS-18092] Option "Restrict trigger to the most recent build" showing trigger for all successful builds not only the most recent

          There are no comments yet on this issue.

            Unassigned Unassigned
            jonasbang Jonas Bang Christensen
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: