(and nothing else yet if Jenkins is good at dependency handling).

2. controller-integration triggers tcpmd5-integration (and unrelated jobs)

I do not think integration job calls another integration job, only a merge calls an integration

... and this is wrong, as shown by the way the jobs behaved when we changed guava version. I ended up re-merging the last odlparent change about 4 times just to trigger integration jobs, which needed to pick up things published by other integration jobs running in parallel.

Since integration jobs publish artifacts, they introduce changes, which absolutely be acted upon by downstream projects. Even when the source code has not changed, the resulting binary artifacts have, which specify things like method signatures, imports, etc. etc. all of which are a cause for downstream rebuilds.

Bye,
Robert