[JIRA] (JENKINS-59938) Active Choices Reactive Parameter with boolean as Referenced parameters is not evaluated depending on the position

56 views
Skip to first unread message

jdanielcano@hotmail.com (JIRA)

unread,
Oct 25, 2019, 12:54:02 PM10/25/19
to jenkinsc...@googlegroups.com
Daniel Cano created an issue
 
Jenkins / Bug JENKINS-59938
Active Choices Reactive Parameter with boolean as Referenced parameters is not evaluated depending on the position
Issue Type: Bug Bug
Assignee: Bruno P. Kinoshita
Attachments: position1.png
Components: active-choices-plugin
Created: 2019-10-25 16:53
Environment: Jenkins 2.190.1 Docker based.
JDK 1.8
Active Choices Plug-in 2.2.1
Labels: 2.190.1-fixed
Priority: Minor Minor
Reporter: Daniel Cano

I have a job with an Active Choice Reactive parameter with a Boolean as a Referenced Parameter

Depending on the position in the job configuration it evaluates the Referenced Parameters or not.

When they are sorted as in the image position1, all works fine. But if the Boolean Parameter is after the Active Choice Reactive parameter, then, the Active Choice Reactive parameter stop working properly. 

I guess it has to evaluate the value of the Boolean Parameter, and if it is after the Active Choice Reactive parameter, the Active Choice Reactive parameter considers that the  the Referenced Parameters does not exists and stop working.

Thanks  a lot in advance.

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

imoutsatsos@msn.com (JIRA)

unread,
Nov 14, 2019, 9:12:02 PM11/14/19
to jenkinsc...@googlegroups.com
Ioannis Moutsatsos commented on Bug JENKINS-59938
 
Re: Active Choices Reactive Parameter with boolean as Referenced parameters is not evaluated depending on the position

Indeed this is how the cascade parameter update happens. Any parameter used by an active choice reactive has to be defined upstream. There are some advanced strategies for sharing parameters independent of their sequence in the form (using an in-memory h2 database) but this is beyond the scope of most typical freestyle jobs.

imoutsatsos@msn.com (JIRA)

unread,
Nov 14, 2019, 9:13:03 PM11/14/19
to jenkinsc...@googlegroups.com

imoutsatsos@msn.com (JIRA)

unread,
Nov 14, 2019, 9:14:03 PM11/14/19
to jenkinsc...@googlegroups.com
Ioannis Moutsatsos edited a comment on Improvement JENKINS-59938
Indeed this is how the cascade parameter update happens. Any parameter used by an active choice reactive has to be defined upstream. There are some advanced strategies for sharing parameters independent of their sequence in the form (using an in-memory h2 database) but this is beyond the scope of most typical freestyle jobs. We have discussed this with [~kinow] as a future improvement.

imoutsatsos@msn.com (JIRA)

unread,
Feb 9, 2020, 8:23:02 AM2/9/20
to jenkinsc...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages