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.

          [JENKINS-21903] Not all maven downstream jobs get triggered

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

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

              Created:
              Updated:
              Resolved: