I have 2 maven 3 multi-module projects (essentially two platform specific full product builds)which trigger a bunch of sub-modules builds, where each sub-moddule is additionally also set up as independent continuous integration jobs. Neither of the maven multi module projects specifies any depedencies, and none of their invoked sub-modules designate a dependency on either of the multi-modudle project's that invoke them. In other words, neither of the multi-module full product builds shoudl be upstream projects of any other job.

I believe these projects to be indentical from a dependency perspective and that jenkins should be simililary designating that neither multi module build has any downstream projects. However, in one of the two full product multi module projects, jenkins properly designate no downstream projects as expected, while in the other, jenkins incorreclty designates many submodules as downstream components, and as such there is a variety of fall out(i.e. chaining and blcoking builds)

The only difference I can identify in the two maven multi-module projects is that each varies in a couple of platform specific modules.

I desire both scenarios to act similarly , where full product build has no downstream projects, and where we can block the product build when a component is building, but where the conitnuous component builds will not block if a full product is building.

I can provide any additional info that may help identify why jenkins thinks my full product builds is an upstream component of my compoennt builds.