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

trigger parameterized builds only triggers the first instance of a project

    Details

    • Similar Issues:
      Show 5 results

      Description

      Configure Job A to trigger Job B twice, with differing parameters. Only the first instance of Job B will be triggered.

      Eg.

      Job A has two triggers:
      Job B, predefined parameter BRANCH=master
      Job B, predefined parameter BRANCH=testbranch

      When Job A finishes building, it will trigger Job B with BRANCH=master, but it will not trigger it a second time with BRANCH=testbranch, as required.

        Attachments

          Issue Links

            Activity

            Hide
            dogfood dogfood added a comment -

            Integrated in plugins_parameterized-trigger #6
            [FIXED JENKINS-8985] Allow multiple ParameterizedDependencys for upstream:downstream.

            Andrew Bayer :
            Files :

            • src/main/java/hudson/plugins/parameterizedtrigger/ParameterizedDependency.java
            Show
            dogfood dogfood added a comment - Integrated in plugins_parameterized-trigger #6 [FIXED JENKINS-8985] Allow multiple ParameterizedDependencys for upstream:downstream. Andrew Bayer : Files : src/main/java/hudson/plugins/parameterizedtrigger/ParameterizedDependency.java
            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: Andrew Bayer
            Path:
            changelog.html
            core/src/main/java/hudson/model/DependencyGraph.java
            core/src/main/java/hudson/tasks/BuildTrigger.java
            http://jenkins-ci.org/commit/jenkins/78c709e91329d4b4ba6f36f25a64412ade63c215
            Log:
            JENKINS-8985 BuildTrigger modification to handle DependencyGroups.

            Pull individual Dependencys out of DependencyGroups we see in
            BuildTrigger.execute and make sure to actually kick those builds off
            as well, so that we can have two different dependencies (say, for
            different parameters) from one upstream project to a single downstream
            project.

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Andrew Bayer Path: changelog.html core/src/main/java/hudson/model/DependencyGraph.java core/src/main/java/hudson/tasks/BuildTrigger.java http://jenkins-ci.org/commit/jenkins/78c709e91329d4b4ba6f36f25a64412ade63c215 Log: JENKINS-8985 BuildTrigger modification to handle DependencyGroups. Pull individual Dependencys out of DependencyGroups we see in BuildTrigger.execute and make sure to actually kick those builds off as well, so that we can have two different dependencies (say, for different parameters) from one upstream project to a single downstream project.
            Hide
            schleprock william schilp added a comment -

            this is more of a nit on the current output from the change. i have job A which triggers Job BuildNVR twice with differing predefined parameters. when Job A triggers the subordinate jobs the output is as such:

            14:52:15 Triggering a new build of BuildNVR #7
            14:52:15 Triggering a new build of BuildNVR #7

            i took this to indicate that only a single BuildNVR job (#7) would be triggered. jenkins did submit two jobs #7 and #8, but it would be nice if the output of job A were correct.

            william schilp

            Show
            schleprock william schilp added a comment - this is more of a nit on the current output from the change. i have job A which triggers Job BuildNVR twice with differing predefined parameters. when Job A triggers the subordinate jobs the output is as such: 14:52:15 Triggering a new build of BuildNVR #7 14:52:15 Triggering a new build of BuildNVR #7 i took this to indicate that only a single BuildNVR job (#7) would be triggered. jenkins did submit two jobs #7 and #8, but it would be nice if the output of job A were correct. william schilp
            Hide
            schleprock william schilp added a comment -

            okay, this is happening on a server with only 2 executors. we're planning on adding more excutors (when we buy some additional ram) and will see what happens with additional executors.

            bill

            Show
            schleprock william schilp added a comment - okay, this is happening on a server with only 2 executors. we're planning on adding more excutors (when we buy some additional ram) and will see what happens with additional executors. bill
            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: Andrew Bayer
            Path:
            changelog.html
            core/src/main/java/hudson/model/DependencyGraph.java
            core/src/main/java/hudson/tasks/BuildTrigger.java
            http://jenkins-ci.org/commit/jenkins/78c709e91329d4b4ba6f36f25a64412ade63c215
            Log:
            JENKINS-8985 BuildTrigger modification to handle DependencyGroups.

            Pull individual Dependencys out of DependencyGroups we see in
            BuildTrigger.execute and make sure to actually kick those builds off
            as well, so that we can have two different dependencies (say, for
            different parameters) from one upstream project to a single downstream
            project.

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Andrew Bayer Path: changelog.html core/src/main/java/hudson/model/DependencyGraph.java core/src/main/java/hudson/tasks/BuildTrigger.java http://jenkins-ci.org/commit/jenkins/78c709e91329d4b4ba6f36f25a64412ade63c215 Log: JENKINS-8985 BuildTrigger modification to handle DependencyGroups. Pull individual Dependencys out of DependencyGroups we see in BuildTrigger.execute and make sure to actually kick those builds off as well, so that we can have two different dependencies (say, for different parameters) from one upstream project to a single downstream project.

              People

              • Assignee:
                abayer Andrew Bayer
                Reporter:
                evilchili evilchili
              • Votes:
                3 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: