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

the projects not order by my order of input

XMLWordPrintable

      such as I have a project as A
      then I set when A finish build, parameterized trigger start C and B project
      but in fact it always first build B not C. seems like Alphabetical not my input order.

      I want to C before B because their build will take about 30min and sometimes I want C first sometimes I want B first, so I won't change the name C to B.(in fact I have about 30+ projects, so it's impossible to set block after someone)

      Sorry for my poor English.

          [JENKINS-16431] the projects not order by my order of input

          cjo9900 added a comment -

          Ordering of the dependencies when triggering downstream is done in the Build trigger (part of core not parametrised trigger plugin)
          And as such does not treat any Downstream job in preference to another unless multiple downstream jobs are also linked, so that a which are triggered by multiple jobs run later.

          i.e. A triggers B and C
          B triggers C

          In this case A would trigger B first as C could be triggered from B also.
          See code @
          https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/tasks/BuildTrigger.java#L199

          If you want jobs to run in priority order i.e. C first then B, have a look at the Priority Sorter Plugin which can cause jobs to run in a preference order when there is limited executors.

          https://wiki.jenkins-ci.org/display/JENKINS/Priority+Sorter+Plugin

          Closing this as this is not a bug
          and is core functionality that expects all jobs to be equal.

          cjo9900 added a comment - Ordering of the dependencies when triggering downstream is done in the Build trigger (part of core not parametrised trigger plugin) And as such does not treat any Downstream job in preference to another unless multiple downstream jobs are also linked, so that a which are triggered by multiple jobs run later. i.e. A triggers B and C B triggers C In this case A would trigger B first as C could be triggered from B also. See code @ https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/tasks/BuildTrigger.java#L199 If you want jobs to run in priority order i.e. C first then B, have a look at the Priority Sorter Plugin which can cause jobs to run in a preference order when there is limited executors. https://wiki.jenkins-ci.org/display/JENKINS/Priority+Sorter+Plugin Closing this as this is not a bug and is core functionality that expects all jobs to be equal.

            cjo9900 cjo9900
            guoyijun163 Coffee Night
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: