Rough guess in the dark, maybe this change is responsible? https://github.com/jenkinsci/p4-plugin/commit/e28412ef5075755c17e96c8172adfd5a2b56905c

We are on Jenkins 2.204.2 and P4 plugin 1.10.9 and its still working for us.  So might just be 1.10.10.  I'll try upgrading next week and see if it breaks on 1.10.10 for us.

Hi tcramer - Thanks for reporting this.

What type of job are you triggering? Freestyle or pipeline?

Please send me screenshots showing the 'Build Triggers' section of the job and the complete URL (with hostname replaced with a dummy hostname) you use to trigger the job.

I will then try and repro this here.

Hi tcramer - Quick update. I just upgraded my test instance to 1.10.10 and for me the trigger is still working so it's possible this is to do with the paths involved or could be Jenkins version related also. If you can get me the data mentioned above and the paths involved that would be great (for example is it a stream, are there spaces, numbers or non ASCII characters). If you'd feel more comfortable in sending the data to me directly please send it to support@perforce.com for my attention.

Hi tcramer

Can you please send me your trigger to 'support@perforce.com'. I want to check how you are calling the trigger.

Thanks in advance,

Karl

I have just checked this. In P4Hook we use an anonymous thread to run the job. If we call getAllItems(to find the list of Jobs) inside the thread it seems to ignore your credentials and return no jobs. We may need to back out https://github.com/jenkinsci/p4-plugin/pull/116/files to fix this.

abutler, are there alternatives for this fix?

Hi msmeeth 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.

I and another colleague have installed 1.10.10 and the triggering still seems to be working as expected for us.

Hi wbrode, can you confirm whether anonymous users have build and read permissions set on your Jenkins server?

The reason I ask is because I've observed that if you allow anonymous users read and build access(or anything higher) on your Jenkins server, the perforce triggers will still work as expected. Whereas if Jenkins is set up to only allow authenticated users read and build access(or higher), that's when I'm see the issue.