Closed skreienk closed 4 months ago
Can you double check if it really is Jenkins 2.452.2? It sounds a lot like #311 and #312
I copied and pasted the version from the about screen in Jenkins. As this is under kubernetes I deleted the pod and associated PVC so that it would download and load everything from scratch. Version 2.452.2.
Possibly same as #319 .
Any way to check?
No.
Closing this, I think it is same as #319.
Jenkins and plugins versions report
Jenkins version: 2.452.2 Plugin version: 2.21
We are setting up our instance of Jenkins under EKS kubernetes, with the seed jobs and all setup being created by the CASC plugin. One of the seed jobs creates the PIMRestore job, pointing to PIMRestore.pipeline, then triggers the first build of the job, which is important as the GenericTrigger config is contained within the pipeline. Here's the seed job snippet:
And here's the GenericTrigger snippet from the pipeline:
After the seed job triggers the first run of PIMRestore the GenericTrigger settings are visible when viewing the job configuration from the Jenkins UI, but they don't work. This is the response when calling the URL:
curl --max-time 30 -vks 'https://${JENKINS_URL}/generic-webhook-trigger/invoke?token=${TOKEN}&DRYRUN=false' (SSL INFO REMOVED FOR BREVITY) < HTTP/1.1 404 Not Found < Date: Wed, 03 Jul 2024 12:51:56 GMT < Content-Type: application/json;charset=utf-8 < Content-Length: 104 < Connection: keep-alive < X-Content-Type-Options: nosniff < Strict-Transport-Security: max-age=31536000; includeSubDomains < { [data not shown]
If I then go and view the configuration of the job in the UI and save it, without changing anything, the GenericTrigger plugin starts working:
curl --max-time 30 -vks 'https://${JENKINS_URL}/generic-webhook-trigger/invoke?token=${TOKEN}&DRYRUN=false' (SSL INFO REMOVED FOR BREVITY) < HTTP/1.1 200 OK < Date: Wed, 03 Jul 2024 14:11:54 GMT < Content-Type: application/json;charset=utf-8 < Content-Length: 185 < Connection: keep-alive < X-Content-Type-Options: nosniff < Strict-Transport-Security: max-age=31536000; includeSubDomains <
I don't understand why I have to view and save the job after it's created to make the GenericTrigger plugin see the config.