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

Hi,

On Fri, Oct 9, 2020 at 2:41 PM Alfredo Moralejo Alonso amoralej@redhat.com wrote:

On Fri, Oct 9, 2020 at 10:39 AM Fabian Arrotin arrfab@centos.org wrote:

...

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

It's working fine now, thanks for your help!

...

We are hitting this again, likely caused by the recent jenkins update [1], Can you check on this, likely need to downgrade the plugin(urltrigger) again.

[1] https://lists.centos.org/pipermail/ci-users/2020-December/002149.html

...

-- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab

---

CI-users mailing list CI-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users

---

CI-users mailing list CI-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users

Thanks and Regards Yatin Karel

Hi,

On Mon, Dec 21, 2020 at 3:07 PM Fabian Arrotin arrfab@centos.org wrote:

On 21/12/2020 06:47, Yatin Karel wrote:

...

Hi,

On Fri, Oct 9, 2020 at 2:41 PM Alfredo Moralejo Alonso amoralej@redhat.com wrote:

...

<snip> >>>>> >>> >>> Can you give it a try ? that plugin was downgraded >>> >> >> It's working fine now, thanks for your help! >> >>> > We are hitting this again, likely caused by the recent jenkins update > [1], Can you check on this, likely need to downgrade the > plugin(urltrigger) again. > > [1] https://lists.centos.org/pipermail/ci-users/2020-December/002149.html >

Vipul announced a jenkins and plugins upgrade for last friday (https://lists.centos.org/pipermail/ci-users/2020-December/002149.html)

I've downgraded URLTrigger plugin to previous version, so can you verify that it now works fine for you ?

Thanks Arrafb, it's working fine now.

BTW, in the future (not needed today), is that possible to also create ticket on https://pagure.io/centos-infra/issues ? that way we'll be sure that it will be tracked when some people are on PTO/away.

Sure will do that, I would have done in this case too but I recalled this email and first thought came to my mind was of using it only as it had full context, but yes agree ticket at pagure.io/centos-infra + email context would also have worked.

Bonus/karma point to then send the mail also on this list pointing to that ticket, for "awareness", so that other projects using the CI env are aware of something changed and existing ticket for it (instead of having to create another one)

+1

-- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab _______________________________________________ CI-users mailing list CI-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users

Thanks and Regards Yatin Karel