Okay, I have project A and project B. Project B happens to be a multi-module maven project. A and B have each one build job defined in Jenkins. A depends on one sub-module of B. I detected the build loop, moved the sub-module from B into a separate job C, but Jenkins is still stuck in that build loop and somehow cannot forget C being part of B...?!

I even checked the dependency by running a maven build with a clean local repo on the command line. There is no loop. And there are no SCM changes. Jenkins just triggers A when finishing B and B when finishing A. Interestingly, the new Job C does not trigger A. However, when B is disabled, C does trigger A....

The fingerprint for C's generated jar artifact lists A and B as being dependent on C (ie. listed in usages section).

After a lot of trying, it seems Jenkins gets its maven dependency information from the modules/ subdirectory structure beneath each job's root directory. I removed B's modules/C directory and now it works......

Not sure how to resolve this. It's not user-friendly/fail safe right now.