On 09/10/2020 08:48, Yatin Karel wrote:
Hi,
On Thu, Oct 8, 2020 at 9:56 PM Fabian Arrotin arrfab@centos.org wrote:
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?
Seems we are hitting[1] caused after [2]. From ci.centos page i see jenkins versions "2.249.1", but was not able to find urltrigger pluggin version, Symptoms looks same as defined in the issue, now("Resolving environment variables using global values") vs earlier("Resolving environment variables using last build values")[3]
[1] https://issues.jenkins-ci.org/browse/JENKINS-60914?jql=project%20%3D%20JENKI... [2] https://github.com/jenkinsci/urltrigger-plugin/commit/82f9e6cfa36dfc8604e7e3... [3] https://ci.centos.org/view/rdo/view/weirdo-pipelines/view/weirdo-promote-pup...
[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
Can you give it a try ? that plugin was downgraded