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

Order Buildque / Block Projects for Upstream Projects

    • Icon: Patch Patch
    • Resolution: Fixed
    • Icon: Major Major
    • other
    • None
    • Platform: All, OS: All

      This patch blocks AbstractProject from beeing build while any tranisitive
      Upstream Project is in the Queue or beeing build.
      Effectivly the buildque is processed in reverse dependency order.

      I would have liked to put this in a plugin rather than a patch but found no easy
      way. If theres a change I can commit the patch I could make the behaviour
      configurable through the hudson configuration page.

          [JENKINS-1938] Order Buildque / Block Projects for Upstream Projects

          martinficker created issue -

          martinficker added a comment -

          Created an attachment (id=296)
          The patch again "main"

          martinficker added a comment - Created an attachment (id=296) The patch again "main"

          Thank you very much for a patch. But for reasons discussed in the ML in the
          past, I'm afraid we can't accept this change.

          As an example, I have a job that replicates the contents of our internal staging
          Maven repository to external mirrors. This is hooked up as a downstream of many,
          many projects.

          Now, I do want this downstream to run each time when any of those upstream
          completes. I don't want the blocking behavior.

          Upstream/downstream is also used to run different stages of a build (like build
          and test) in parallel. This patch kills the efficiency gain in doing this.

          We do need to make some improvements for the diamond dependency case, but I'm
          afraid this is not the solution.

          Kohsuke Kawaguchi added a comment - Thank you very much for a patch. But for reasons discussed in the ML in the past, I'm afraid we can't accept this change. As an example, I have a job that replicates the contents of our internal staging Maven repository to external mirrors. This is hooked up as a downstream of many, many projects. Now, I do want this downstream to run each time when any of those upstream completes. I don't want the blocking behavior. Upstream/downstream is also used to run different stages of a build (like build and test) in parallel. This patch kills the efficiency gain in doing this. We do need to make some improvements for the diamond dependency case, but I'm afraid this is not the solution.
          Kohsuke Kawaguchi made changes -
          Resolution New: Won't Fix [ 2 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          mdonohue made changes -
          Link New: This issue depends on JENKINS-2072 [ JENKINS-2072 ]

          mdonohue added a comment -
              • Issue 3388 has been marked as a duplicate of this issue. ***

          mdonohue added a comment - Issue 3388 has been marked as a duplicate of this issue. ***
          mdonohue made changes -
          Link New: This issue is duplicated by JENKINS-3388 [ JENKINS-3388 ]

          mdonohue added a comment -
              • Issue 4137 has been marked as a duplicate of this issue. ***

          mdonohue added a comment - Issue 4137 has been marked as a duplicate of this issue. ***
          mdonohue made changes -
          Link New: This issue is duplicated by JENKINS-4137 [ JENKINS-4137 ]

          mdonohue added a comment -
              • Issue 4365 has been marked as a duplicate of this issue. ***

          mdonohue added a comment - Issue 4365 has been marked as a duplicate of this issue. ***
          mdonohue made changes -
          Link New: This issue is duplicated by JENKINS-4365 [ JENKINS-4365 ]

            Unassigned Unassigned
            martinficker martinficker
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: