When I try to use a Boolean parameter as a reference parameter to an Active Choice Reactive Parameter, it never evaluates to "on". I am using Jenkins version: 1.625.1 I am using latest version of Active Parameter plugin I am using jQuery plugin version: 1.11.2-0
Attached please find a example config.xml of a job I have tested on.
When I try to use a Boolean parameter as a reference parameter to an Active Choice Reactive Parameter, it never evaluates to "on". I am using Jenkins version: 1.625.1
I am using latest version of Active Parameter plugin (1.2)
I am using jQuery plugin version: 1.11.2-0
Attached please find a example config.xml of a job I have tested on.
Could not reproduce it. The script seems to be working as expected. By the default the checkbox is not checked, and the single select value is false. Then if you check the boolean parameter, the cascaded parameter changes its value to true. Firefox 43.0, Ubuntu Server LTS 14.04.3.
Thanks Gil. I have Chrome and Chromium here, and Safari and IE at work. Let me know if that work or not, and I will confirm what happens in my environment with the other browsers (I can do that anyway in some hours or during the next week). Cutting last release of year in the next days
Tested it with FF but still same behavior. I have tried to set the default value of the Boolean reference true and now when I press on the "build with parameters" link, it does evaluates to "on" but when I uncheck the Boolean reference, it does not evaluates to other than "on". That is very strange. The only thing that is still different in my environment is the Jenkins version. I have tried to read the changelog but couldn't find anything about Boolean parameters or something like that. I'll try to upgrade the Jenkins version to the latest LTS later on today but I doubt it'll solve my issue. I really have no clue.
I have tried to set the default value of the Boolean reference to true and now when I press on the "build with parameters" link, it does evaluates to "on" but when I uncheck the Boolean reference, it does not evaluates to other than "on". That is very strange. The only thing that is still different in my environment is the Jenkins version. I have tried to read the changelog but couldn't find anything about Boolean parameters or something like that.
I'll try to upgrade the Jenkins version to the latest LTS later on today but I doubt it'll solve my issue. I really have no clue.