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

DependecyDeclarer always triggers builds and without Actions

    Details

    • Type: Improvement
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: core
    • Labels:
      None
    • Environment:
      Hudson 1.340
    • Similar Issues:

      Description

      Currently Build.RunnerImpl.cleanUp() calls BuildTrigger.execute().. this triggers ALL jobs that have been added as downstream jobs by any DependecyDeclarer (yes, the class name has a typo).. only BuildTrigger itself gets any special handling: triggering only if status threshold is met.. if the downstream connection is made by any other impl, it will trigger the job always, even if this build failed or was aborted! Furthermore, downstream jobs are triggered with just UpstreamCause, with no opportunity for those Declarers to provide any additional Actions (like build parameters).

      Need to expand this API so Declarers can control whether a build is triggered and provide Actions to submit with the build.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                mindless Alan Harder
                Reporter:
                mindless Alan Harder
              • Votes:
                1 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: