Hi, On Thu, Oct 8, 2020 at 9:56 PM Fabian Arrotin <arrfab at 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%20JENKINS%20AND%20component%20%3D%20urltrigger-plugin%20ORDER%20BY%20updated%20DESC%2C%20priority%20DESC%2C%20created%20ASC [2] https://github.com/jenkinsci/urltrigger-plugin/commit/82f9e6cfa36dfc8604e7e31e2afa4d5d59a987e7 [3] https://ci.centos.org/view/rdo/view/weirdo-pipelines/view/weirdo-promote-puppet-centos8-victoria/job/weirdo-promote-puppet-centos8-victoria-properties/39/triggerCauseAction/ > > [1] > > https://ci.centos.org/view/rdo/view/weirdo-pipelines/view/weirdo-promote-test-puppet-centos8/job/weirdo-promote-puppet-centos8-properties/ > > [2] > > https://ci.centos.org/view/rdo/view/weirdo-pipelines/view/weirdo-promote-test-puppet-centos8/job/weirdo-promote-puppet-centos8-properties/1574/ > > [3] > > https://ci.centos.org/view/rdo/view/weirdo-pipelines/view/weirdo-promote-test-puppet-centos8/job/weirdo-promote-puppet-centos8-properties/1576/ > > > > 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. > > > -- > Fabian Arrotin > The CentOS Project | https://www.centos.org > gpg key: 17F3B7A1 | twitter: @arrfab > > _______________________________________________ > CI-users mailing list > CI-users at centos.org > https://lists.centos.org/mailman/listinfo/ci-users Thanks and Regards Yatin Karel