"Single triggered job" option. How does it work?

Question

"Single triggered job" option. How does it work?

x4team opened this issue 9 months ago · comments

Hi, everybody
In the 3.0 version of the plugin, the developers added the option "Single triggered job", which can be configured in Manage Jenkins -> System and it has only one field WITHOUT a DESCRIPTION of its work. Also in changelog I did not find a description of this option ((

I have several jobs, and some of them have several repositories with a web hook. I want only one (or a limited number) jobs to run with this web hook. Is this an option about this?
I tested this "Single triggered job" option and entered only my helm-upgrade job in this field. But unfortunately it didn't work, all jobs were started, where there was the same repository

Christian Del Monte · Answer 1 · Mon Oct 30 2023 22:58:43 GMT+0800 (China Standard Time)

Hi @solarlodge, maybe can you help @x4team ?

Tnx! :)

Christian Del Monte · Answer 2 · Mon Oct 30 2023 23:11:52 GMT+0800 (China Standard Time)

@x4team In the readme (Jenkins Global Configurations) there is a brief explanation of this new feature:

you can configure a single job to be triggered exclusively. That overrides the default behavior of having a dedicated endpoint (+ some internal matching logic) for ALL pipelines to be triggered via this plugin. In case of a non-existing job a WARNING will be logged at global jenkins log. You can omit this feature by simply leaving this field blank.

Christian Brauchmann · Answer 3 · Tue Oct 31 2023 01:14:28 GMT+0800 (China Standard Time)

hi @x4team :)
this feature is intended to one configure and ONLY one job to triggered via your configured hook endpoint.
the jobname needs to be the full path name. You can check this via your jenkins instance's groovy concsole via
println Jenkins.instance.allItems.find { it.fullName.contains('PART_OF_YOUR_JOBNAME') }.fullName e.g.
In case of a non-existing job there should be a warning in your jenkins log.

Dmitry Rakov · Answer 4 · Tue Oct 31 2023 16:39:20 GMT+0800 (China Standard Time)

hi @x4team :) this feature is intended to one configure and ONLY one job to triggered via your configured hook endpoint. the jobname needs to be the full path name. You can check this via your jenkins instance's groovy concsole via println Jenkins.instance.allItems.find { it.fullName.contains('PART_OF_YOUR_JOBNAME') }.fullName e.g. In case of a non-existing job there should be a warning in your jenkins log.

Hi @solarlodge , @cdelmonte-zg , thanks for the help
Via Jenkins.instance.AllItems.. I found joba's name as "Dev/Category/helm-upgrade",and inserted it into the settings of the Bitbucket PPR plugin (field "Single triggered job"). Next I pushed commit to "helm" repository, and I saw that not only the "helm-upgrade" job was launched, but also all the release ones

Are my actions correct?

Christian Brauchmann · Answer 5 · Tue Oct 31 2023 18:26:21 GMT+0800 (China Standard Time)

@x4team Looks correct. Out of curiosity:
Does it work when you configure it, save and restart your whole jenkins instance AFTERWARDS?

Dmitry Rakov · Answer 6 · Tue Oct 31 2023 20:03:14 GMT+0800 (China Standard Time)

@x4team Looks correct. Out of curiosity: Does it work when you configure it, save and restart your whole jenkins instance AFTERWARDS?

YES, thanks. This solved my problem 🤝

Christian Del Monte · Answer 7 · Wed Nov 01 2023 19:44:48 GMT+0800 (China Standard Time)

More docus will be added in the next release of the plugin