On 07/10/2020 12:50, Alfredo Moralejo Alonso wrote:
Hi,
We are hitting some strange issue in some of the CloudSIG jobs since october, 5th.
We have some parameterized jobs triggered by URLTrigger [1]. Until a couple of days ago, those jobs were executed with default values for each parameter [2] but now, when the job is triggered by URLTrigger the parameters are not passed at all to the job [3]. If i use "Build with parameters" manually, the job runs fine using default values.
Is anyone hitting similar issues? any hint of what may be the problem?
[1] https://ci.centos.org/view/rdo/view/weirdo-pipelines/view/weirdo-promote-tes... [2] https://ci.centos.org/view/rdo/view/weirdo-pipelines/view/weirdo-promote-tes... [3] https://ci.centos.org/view/rdo/view/weirdo-pipelines/view/weirdo-promote-tes...
Best regards,
Alfredo
Hi Alfredo,
Just seeing now this mail . That's probably an artifact of the hardware issue we had (see previous mail) and jenkins relocate/update. That caused one or two issues with some updated plugins, so worth verifying if the urltrigger plugin works as expected with the jenkins lts version now running on ci.centos.org.
PS : we still consider that jenkins setup "legacy" and reason why projects are encouraged to move to the new openshift/OCP setup, so that they can have their own jenkins in their own namespace, and not suffer from compatibility matrix issue with *all* plugins actually deployed on one jenkins.