Description of problem:

Per an exchange with an internal consumer at https://coreos.slack.com/archives/CNU6JC8GJ/p1639018303084900

The are extending our 4.8 Jenkins image, and with the latest version, have started seeing this NPE (full stack trace in slack thread):

java.lang.NullPointerException
	at io.fabric8.jenkins.openshiftsync.PipelineJobListener.upsertWorkflowJob(PipelineJobListener.java:169)
	at io.fabric8.jenkins.openshiftsync.PipelineJobListener.upsertItem(PipelineJobListener.java:148)
	at io.fabric8.jenkins.openshiftsync.PipelineJobListener.onCreated(PipelineJobListener.java:90)
	at hudson.model.listeners.ItemListener.lambda$fireOnCreated$1(ItemListener.java:217)
	at hudson.model.listeners.ItemListener.forAll(ItemListener.java:178)
	at hudson.model.listeners.ItemListener.fireOnCreated(ItemListener.java:215)
	at hudson.model.ItemGroupMixIn.createProjectFromXML(ItemGroupMixIn.java:291)
	at jenkins.model.Jenkins.createProjectFromXML(Jenkins.java:4096)


at this time, this maps to this line in the method:

String ns = property.getNamespace();

where that property object was previously populated by

 BuildConfigProjectProperty property = buildConfigProjectForJob(job);


So why is the BuildConfigProjectProperty not associated with the job?
1) they are creating a project ... perhaps there is a timing issue and the BuildConfigProjectProperty is not created yet?
2) the plugin combination they have constructed is somehow breaking other function
3) this in fact is not a jenkins pipeline strategy job, and we should just ignore.

Minimally, we should move the get Namespace call in the if block with the null check.

We then need to consider whether we put this create event in a queue to periodically retry.