-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
Platform: All, OS: All
We have several Maven2 projects set up. Hudson, after parsing the poms, knows
the downstream and upstream projects. So normally, the downstream project should
be build after the upstream project finished. But instead the downstream is
triggered too early.
Also when doing the cvs polling and a project and its downstream project has
updates, the downstream project gets build twice. One is the cvs trigger and the
second one the upstream trigger. I think the cvs trigger should be discarded
when the upstream project is build, shouldn't it?
- duplicates
-
JENKINS-2736 Inefficient build order for Maven2 projects
- Closed