<p>Although I haven't tried using the Parameterized Scheduler in particular, I don't think you will be able to use this plugin to trigger a build with Active Choice parameters - most plugins don't support passing Active Choice parameters to builds.  There is currently <a href="https://issues.jenkins-ci.org/browse/JENKINS-28735" rel="nofollow noreferrer">an open bug report on this issue</a>.</p>

<p>As for a workaround - I have been able to successfully trigger builds with Active Choice parameters using the HTTP REST API <code>/build</code> endpoint (a bit counterintuitively, NOT <code>/buildWithParameters</code>).  So for instance you could have a second job that runs on a schedule and does nothing but hit the API endpoint to trigger the job and pass parameters, or you could have a plain Unix cronjob that hits the endpoint, or something else along those lines.</p>

CC BY-SA 4.0
2020-02-10T07:14:08.713Z
2020-02-10T07:14:08.713Z
jayhendren
<p>I have created a Jenkins job which have Choice Parameters, Active Choice Parameters, Active choice reactive params and Reactive reference params.</p>
<p>This job needs to be scheduled with parameters.</p>
<p>As the active choice params and reactive choice params are dynamically executed with groovy scripts.</p>
<p>How can I pass these parameters to schedule a job with cron present in Jenkins.</p>
<p>I'm using <a href="https://plugins.jenkins.io/parameterized-scheduler" rel="nofollow noreferrer">Parameterized Scheduler</a> plugin for scheduling.</p>
<p><strong>EDIT</strong></p>
<p>Say I have a job which have</p>
<p>1 Active choice parameter PARAM_A</p>
<p>1 Active choice reactive parameter PARAM_B</p>
<p>2 active choice reactive reference parameters PARAM_C and PARAM_D.</p>
<p>I tried by hard coding active choice parameter in the cron like below</p>
<pre><code>15 7 * * * % PARAM_A=somestring
</code></pre>
<p>But with the provided active choice value, the job is getting failed.
Because the <strong>reactive reference parameters</strong> which were written in groovy script are not getting executed when i triggered with scheduler in jenkins.</p>
<p>In a jenkins schedule job using parameterized-scheduler, where if we give input</p>

CC BY-SA 4.0
2020-02-07T20:03:34.530Z
can you clarify more on this question?
Samit
CC BY-SA 4.0
2020-02-12T06:34:53.227Z
I have updated the question, please let me know, If you need anything mroe
Jman91
<jenkins>
Schedule Jenkins Job with Active choice Reactive parameters and Reactive reference parameters
Jman91
# Schedule Jenkins Job with Active choice Reactive parameters and Reactive reference parameters

(Asked by: username_0 on 2020-02-06)

I have created a Jenkins job which have Choice Parameters, Active Choice Parameters, Active choice reactive params and Reactive reference params.
This job needs to be scheduled with parameters.
As the active choice params and reactive choice params are dynamically executed with groovy scripts.
How can I pass these parameters to schedule a job with cron present in Jenkins.
I'm using Parameterized Scheduler plugin for scheduling.
EDIT
Say I have a job which have
1 Active choice parameter PARAM_A
1 Active choice reactive parameter PARAM_B
2 active choice reactive reference parameters PARAM_C and PARAM_D.
I tried by hard coding active choice parameter in the cron like below
15 7 * * * % PARAM_A=somestring

But with the provided active choice value, the job is getting failed.
Because the reactive reference parameters which were written in groovy script are not getting executed when i triggered with scheduler in jenkins.
In a jenkins schedule job using parameterized-scheduler, where if we give input

**Tags:** jenkins

> **Comments:**
> **username_1**: can you clarify more on this question?  
> **username_0**: I have updated the question, please let me know, If you need anything mroe  

---

## 1 answers

### Answer by username_2 on 2020-02-10. Score: 1

Although I haven't tried using the Parameterized Scheduler in particular, I don't think you will be able to use this plugin to trigger a build with Active Choice parameters - most plugins don't support passing Active Choice parameters to builds. There is currently [an open bug report on this issue](https://issues.jenkins-ci.org/browse/JENKINS-28735).

As for a workaround - I have been able to successfully trigger builds with Active Choice parameters using the HTTP REST API `/build` endpoint (a bit counterintuitively, NOT `/buildWithParameters`). So for instance you could have a second job that runs on a schedule and does nothing but hit the API endpoint to trigger the job and pass parameters, or you could have a plain Unix cronjob that hits the endpoint, or something else along those lines.


---

