openshift-sync 1.0.24 build decision handler results in triggered jenkins workflow job in both source and synced jenkins instances

[afe...@bandwidth.com]

The openshift-sync plugin can sync multiple OpenShift projects' JenkinsPipelineStrategy BuildConfigs to a single Jenkins instance ...

• By default, the project running Jenkins is monitored, but additional projects can be monitored by adding them to the Namespace list in the "Manage Jenkins" -> "Configure System" section for this plugin. NOTE: the service account associated with the Jenkins deployment must have the edit role for each project monitored

however I believe there is a pre-existing corner case when the remote projects monitored also run Jenkins causing the BuildDecisionHandler logic to trigger a redundant pipeline execution in the remote project potentially causing problems for people.

Has anyone else ran into this before?  Since I can see about relocating where BuildConfigs live within our OS projects, I can work around this, but it would be good to see if there should be a fix or something done for it.