Parameterized Scheduler Not Kicking Off

[Saieph]

Hello. I'm not entirely sure where to turn. The basic gist of this is:

• I have a job in Jenkins that is parametrized with Choice Parameters.
• When I exclude the parameters and run on the Jenkins scheduler, the jobs kick off fine
• When I execute with parameters on a schedule using this plugin, and I use only ONE parameter (choice parameter) the job kicks off as scheduled
• As soon as I include two parameters, the parameterized scheduler stops kicking off the jobs.

Any ideas?

[jwmach1]

Was there any information in the Jenkins Log? https://wiki.jenkins-ci.org/display/JENKINS/Logging. I don't remember how to enable "fine" logging. See what you can find around the jenkins docs.

On Tue, May 31, 2016 at 4:12 PM, Gashzilla [email protected] wrote:

Hello. I'm not entirely sure where to turn. The basic gist of this is:

• I have a job in Jenkins that is parametrized with Choice Parameters.
• When I exclude the parameters and run on the Jenkins scheduler, the jobs kick off fine
• When I execute with parameters on a schedule using this plugin, and I use only ONE parameter (choice parameter) the job kicks off as scheduled
• As soon as I include two parameters, the parameterized scheduler stops kicking off the jobs.

Any ideas?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/jwmach1/parameterized-scheduler/issues/4, or mute the thread https://github.com/notifications/unsubscribe/ABJI9N4u0BQWcG_iO1EQtceLz6Z4_3sXks5qHKQ_gaJpZM4Iq9rp .

[stewartbryson]

Did you ever figure this out. Happening to me now.

[wandergeek]

Same here.

[urusha]

Confirming. There must be no spaces between semicolon and the second parameter name. The one like this should work: * * * * * % PARAM1=value1 ;PARAM2=value2

[ludwigm]

We figured out that if you define multiple entries the time must also differ so that the jobs are scheduled. This is not totally obvious

[ghost]

I have a Jenkins job with Choice parameter and schedule looks like this 0 14 * * * %name=value

However, build does not seem to be triggered at all. Does anyone have any idea ?

[jwmach1]

So, your goal is to run this build on the zero'd minute of the fourteenth hour -- 14:00 (2pm)? cron doc Does the build have a parameter named 'name'? Make sure that parameter name is the same you used to configure the build. Also, play with the white space around the %.

check your Jenkins system logs messages.

Clearly, the parsing logic could be better. :-)

[gilShin]

Has anyone figured this out? Doesn't work for me as well. Plugin version 0.5. Jenkins version 2.60.2 In the logs I see: "aborted (scm manipulator not settled !)" for this job. This is a free style job with one string parameter. I have tried both: H/2 * * * * % GIL=mosh

and H/2 * * * * %GIL=mosh

The parameter name is GIL.

[gilShin]

Restarting Jenkins (Maybe it is better to add it as a prerequisite for the plugin installation?) solved the problem.

[sustacek]

Restarting Jenkins (Maybe it is better to add it as a prerequisite for the plugin installation?) solved the problem.

Oh for *'s sake add "restart needed" to installation of this plugin. I just spent an hour figuring out why it is not working. Plugin's installation did not say anything about needed restart, unlike some other plugins, so I didn't do it.

[xxxvodnikxxx]

Hi, even if you properly restart Jenkins, periodic scheduler seems not to work properly seems also not to work completely with a single param :

• I noticed it was probably triggered only once , using H 2 * * 1-5 % GENERATE_BASELINE=false; SERVER=${SERVER}

And jenkins v2.164.3

[xxxvodnikxxx]

Any update, please ?

[vibhavagrawal]

Oh for *'s sake add "restart needed" to installation of this plugin. I just spent an hour figuring out why it is not working. Plugin's installation did not say anything about needed restart, unlike some other plugins, so I didn't do it.

Hey @sustacek, @gilShin, I see that plugin is working without restart in general (env=uat), but only this use case of passing two comma-separated values for a CHOICE type field is not working. (env=uat1,uat2) When you said it worked after restart, did it work for the case of multiple values for CHOICE field or in general for the plugin?

[sustacek]

Hi @vibhavagrawal, unfortunately I cannot recall any details after nearly 2 years (based on the stamp on my comment), sorry. I don't know if I used two values or one or really any details now.

[salman8328]

did any one get it to work ? It is not working for me : tried : triggers { parameterizedCron(''' 11 * * * 1 % TRIGGERED_BY_DAILY_TIMER=True; TRIGGERED_BY_MONTHLY_TIMER=False 54 * * * 1 % TRIGGERED_BY_MONTHLY_TIMER=True; TRIGGERED_BY_DAILY_TIMER=False ''') }

tried this as well:

triggers {
    parameterizedCron('''
    11 * * * 1 %TRIGGERED_BY_DAILY_TIMER=True;TRIGGERED_BY_MONTHLY_TIMER=False
    54 * * * 1 %TRIGGERED_BY_MONTHLY_TIMER=True;TRIGGERED_BY_DAILY_TIMER=False
    ''')
}

[ashpratap007]

Facing a similar issue, anyone found a fix for this?