Status: Resolved (View Workflow)
Platform: PC, OS: All
I have a multi modules maven project
I launch a hudson job for this project with multiple maven2 goals:
test pmd:pmd cobertura:cobertura
The post action (build another job) doesn't work even if i checked
the box "trigger even the build is unstable"
My project seems unstable (yellow)
but the job after is never launched
JENKINS-4739 Build other projects: "Trigger even if the build is unstable" doesn't work
- is duplicated by
JENKINS-3884 Maven2 job does not trigger subsequent jobs when failing tests
- is related to
JENKINS-3122 auto build of downstream projects doesn't workfor m2 jobs in unstable state, when using surefire flag testFailureIgnore
Ok, on further investigation, this is more confusing than I thought. =) The
problem here is that the m2 projects' "build when SNAPSHOT dependency builds"
option feeds into the same mechanics as the post-build trigger (and, for that
matter, the "build modules in parallel" option relies on the same mechanics as
well). I'm not sure if we really want the post-build trigger configuration to be
doing anything to the m2 project-specific dependency build logic, and there's no
clear way to distinguish between "this project is an m2 project-type dependency"
and "this project is a build trigger-type dependency". Not to mention that the
same project could show up in both categories.
Let me think on this some.
JENKINS-4739, which is already fixed.
Patch looks good - I'll put it through some testing tomorrow and (assuming no
problems) commit it then, in which case the fix should be live in 1.318.