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

Downstream job should only start executing after upstream was already build

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Not A Defect
    • Icon: Major Major
    • downstream-ext-plugin
    • None

      I have project A that triggers project B only if it has SVN changes (using the downstream-ext plugin).

      Project B is set to be triggered by SVN changes as well.

      My problem is that most of the time when I do a commit on both repositories (a commit that is meant as a whole), project B will start building before project A, even though this plugin marks it as downstream.

      It would be nice that B (when it detects a trigger other the A having been built) checks to see if A has changes and needs to build. If it has changes it makes sure A runs before continuing. It should do this until A no longer has the need to build and only then it should update and run B.

      In my current config B always or almost always runs too soon, before A prepares some resources for it... So it's a wasted run + then it won't build again after the correct changes are build in A because B was already updated.

      Hope this long story makes sense .

            kutzi kutzi
            costescuandrei Andrei Costescu
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: