-
Bug
-
Resolution: Unresolved
-
Minor
-
Active Choices Plug-in version 1.4
Jenkins ver. 1.652
I have an Active choice parameter (Multi select) with the following Groovy script
['ONE:selected','TWO:selected','TREE:selected','FOUR:selected']
And the following fallback
['FALLBACK']
If I start the job with a timer the parameter gets the value ONE:selected, I was expecting ONE,TWO,TREE,FOUR
This is related to JENKINS-32405 and JENKINS-28735, but has no relation to other Active choice parameters so it might be an easier fix.
- is related to
-
JENKINS-28735 Supporting Jobs triggered by plug-ins, API and scripts, timer
-
- Reopened
-
Hi Mattias,
Thanks for reporting this issue, and for including some Groovy example code to reproduce it.
The script is evaluated, and the choices returned are: [ONE:selected, TWO:selected, TREE:selected, FOUR:selected]
I believe the way that the plug-in is treating timer/remote/chained job executions isn't ideal yet. So I'm not sure how to fix your issue right now.
Will cut a new release, but wanted to provide you some feedback. And as my memory is quite bad, this works as a note to myself, so that in the future when I try to think about a workaround for this issue (and for that one you linked here) I'll re-start from here
Feel free to ping this issue should you have any suggestions on how to fix it, or any more information that you find may be useful.
Cheers,
Bruno