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

downstream trigger

XMLWordPrintable

    • Icon: New Feature New Feature
    • Resolution: Unresolved
    • Icon: Minor Minor
    • join-plugin
    • None

      Per Bill Koester comment on http://wiki.jenkins-ci.org/display/JENKINS/Join+Plugin

      For a parallel job (one that is a child of the root job) it would be helpful if that job looked to see who triggered it. If the root/upstream project triggered it then the join plugin would continue as normal. If anything else triggered the build (ie. scm or manual) then it would build the downstream job after successful completion. As suggested a simple checkbox, that it activated within the child job, could turn on/off this behavior.

          [JENKINS-8450] downstream trigger

          mdonohue added a comment -

          I think this is outside the scope of what the join plugin is intended to do. If you don't always want the join behavior, but find it convenient for optimizing the overall flow of your jobs, then I think you want to enable the block-when-upstream-building feature. See JENKINS-1938.

          mdonohue added a comment - I think this is outside the scope of what the join plugin is intended to do. If you don't always want the join behavior, but find it convenient for optimizing the overall flow of your jobs, then I think you want to enable the block-when-upstream-building feature. See JENKINS-1938 .

            mdonohue mdonohue
            cgreen cgreen
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated: