-
Bug
-
Resolution: Not A Defect
-
Minor
-
None
-
P4 Plugin Version1.14.1
Jenkins Version 2.387.2
Pipeline: Multibranch Version 746.v05814d19c001
Hi,
I have the trigger setup and it will trigger a normal pipeline but not a multibranch pipeline:
May 12, 2023 5:35:26 PM INFO org.jenkinsci.plugins.p4.trigger.P4Hook doChange
Received trigger event for: ssl:10.156.0.9:1666
May 12, 2023 5:35:26 PM INFO org.jenkinsci.plugins.p4.trigger.P4Hook probeJobs
P4: probing: perry_sandbox_2
May 12, 2023 5:35:26 PM INFO org.jenkinsci.plugins.p4.trigger.P4Trigger poke
P4: poking: perry_sandbox_2
May 12, 2023 5:35:27 PM INFO org.jenkinsci.plugins.p4.workspace.StreamWorkspaceImpl setClient
P4: Creating stream client: jenkins-master-perry_sandbox_2-0
`perry_sandbox_2` being regular pipeline job, `perry_sandbox` is a multibranch pipeline job that isn't triggered.
Looking at this line I'm assuming the multibranch doesn't have a P4Trigger.
The regular pipeline job has a "P4 Trigger Log" and explicit option for "Perforce Triggered Build". The multibranch pipeline has a scan log that isn't being updated on trigger and not an explicit option though it does have some filtering (which I tried adding and setting to `.*`).
The docs say this works but I'm not finding anything that can trigger it.