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

Not all maven downstream jobs get triggered


    • Similar Issues:


      We have a maven job Foo with 10 downstream dependencies. In the Job page all the dependencies are noted clearly as well as on the the actual build page. Hower some of the downstream Jobs show with "(none)" instead of their build number and the log of the Foo build shows the "Triggering a new build of xxxx" lines, but only for 7 out of the 10 that should be triggered.

      Jenkins clearly knows about the SNAPSHOT dependency and shows the downstream relationship correctly, yet it 'forgets' to trigger some of the jobs.

      Confirmed with 1.550 and 1.551.


          Issue Links


            sodul Stephane Odul created issue -
            jglick Jesse Glick made changes -
            Field Original Value New Value
            Link This issue is duplicated by JENKINS-13601 [ JENKINS-13601 ]
            jglick Jesse Glick made changes -
            Labels snapshot trigger
            Assignee olamy [ olamy ] Jesse Glick [ jglick ]
            Component/s maven-dependency-update-trigger [ 15756 ]
            jglick Jesse Glick made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            scm_issue_link SCM/JIRA link daemon made changes -
            Status In Progress [ 3 ] Resolved [ 5 ]
            Resolution Fixed [ 1 ]
            jglick Jesse Glick made changes -
            Link This issue depends on JENKINS-26450 [ JENKINS-26450 ]
            rtyler R. Tyler Croy made changes -
            Workflow JNJira [ 153904 ] JNJira + In-Review [ 194747 ]


              • Assignee:
                jglick Jesse Glick
                sodul Stephane Odul
              • Votes:
                1 Vote for this issue
                5 Start watching this issue


                • Created: