Details
-
Type:
Bug
-
Status: Open (View Workflow)
-
Priority:
Major
-
Resolution: Unresolved
-
Component/s: p4-plugin
-
Labels:None
-
Environment:Jenkins LTS 2.204.2 on Windows Server 2016 (64bit)
Java 1.8.0_144-b01
p4-plugin 1.10.10
-
Similar Issues:
Description
We use a Perforce Trigger that calls curl to POST to the /p4/change endpoint exposed by the p4-plugin. With 1.10.6, this trigger worked, and the relevant job would run. Upgrading to 1.10.10, and the trigger stopped working.
In investigating the issue, 1.10.10 was still logging "doChange: Received trigger event for: <p4port here>", but the usual followup log "probeJobs: P4: probing: <jenkins job>" never appeared. Rolling the plugin back to 1.10.6 restored the ability to trigger the jenkins job.
Hi Matthew Smeeth apologies if this has caused a regression. I'm unable to reproduce the issue on our instance of Jenkins (version 2.190.3) and am not in a position to upgrade it at the moment to do further testing due to it being a corporate instance, so it's going to be difficult for me to come up with alternatives at this time.
I think that your only option is to back this change out for the time being.