When a job definition is published, triggers schedule builds on target instance. I am not sure there is any usecase when this is expected. But when target instance is mare passive result presenter, this behaviour is undesirable.

I have not tested the scenario when the build is actually built on target instance and the build number clashes with incoming build from source instance.