• Type: Bug
• Resolution: Duplicate
• Priority: Major
• Component/s: maven-plugin
• Labels:

  None
• Environment:

  Debian Squeeze, 2.6.32-5 x64, Tomcat6

[JENKINS-13601] Jenkins maven job does not trigger all downstream jobs

Pit Skywalker created issue - 2012-04-25 21:20

Pit Skywalker made changes - 2012-04-25 21:21

Description

Original: Project1 has dependencies in its pom.xml, that are listed as Upstream Jobs in Jenkins job for Project1. And vice versa, Project1 is listed in Downstream Jobs list in every dependent Jenkins job. But when by any trigger depenndent jobs start, when they finish, they do not a) trigger all jobs, just one, and b) Project1 job is not triggered at all (so CI is lost for this particular job)

New: Project1 has dependencies in its pom.xml, that are listed as Upstream Jobs in Jenkins job for Project1. And vice versa, Project1 is listed in Downstream Jobs list in every dependent Jenkins job. But when by any trigger dependent jobs start, when they finish, they a) do not trigger all jobs, just one, and b) Project1 job is not triggered at all (so CI is lost for this particular job)

Jesse Glick made changes - 2014-08-20 18:07

Link

New: This issue duplicates JENKINS-21903 [ JENKINS-21903 ]

Jesse Glick made changes - 2014-08-20 18:07

Resolution		New: Duplicate [ 3 ]
Status	Original: Open [ 1 ]	New: Resolved [ 5 ]

Jenkins IRC Bot made changes - 2014-09-27 18:27

Component/s		New: maven-plugin [ 16033 ]
Component/s	Original: maven2 [ 15487 ]

R. Tyler Croy made changes - 2016-07-25 23:54

Workflow

Original: JNJira [ 144068 ]

New: JNJira + In-Review [ 190892 ]