The openshift-sync plugin <https://github.com/jenkinsci/openshift-sync-plugin/tree/openshift-sync-1.0.24#other-configuration> 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 <https://github.com/jenkinsci/openshift-sync-plugin/blob/openshift-sync-1.0.24/src/main/java/io/fabric8/jenkins/openshiftsync/BuildDecisionHandler.java> logic to trigger a redundant pipeline execution in the remote project potentially causing problems for people. [image: openshift-sync 1.0.24 BuildDecisionHandler race condition.png] <about:invalid#zClosurez> 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. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/c0585332-14a6-4420-be3f-7e1a3af5dbfc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
