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

PeepholePermalink RunListenerImpl oncompleted should be triggered before downstream builds are triggered

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • core
    • None

      Scenario
      ProjectA triggers ProjectB
      ProjectB has a RunParameter for ProjectA with a filter set for Successful Builds Only. The Run Parameter uses the PeepholePermalink to determine the LastSuccessful build.

      When ProjectA completes successfully, it will trigger a build of ProjectB before the PeepholePermalink cache is updated. This causes the RunParameter to default to the previous successful build of ProjectA, not the one which has just completed.

            olivergondza Oliver Gond┼ża
            gcummings Geoff Cummings
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: