Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-32044

Fail to evaluate Boolean parameter to "on" when checked

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      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.

        Attachments

          Activity

          Hide
          gils Gil Shinar added a comment -

          So maybe the issue is with chrome?
          I'll test that with FF

          Show
          gils Gil Shinar added a comment - So maybe the issue is with chrome? I'll test that with FF
          Hide
          kinow Bruno P. Kinoshita added a comment -

          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

          Show
          kinow Bruno P. Kinoshita added a comment - 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
          Hide
          gils Gil Shinar added a comment - - edited

          Tested it with FF but still same behavior.
          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.

          Show
          gils Gil Shinar added a comment - - edited Tested it with FF but still same behavior. 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.
          Hide
          kinow Bruno P. Kinoshita added a comment -

          Fixed in 1.3

          Show
          kinow Bruno P. Kinoshita added a comment - Fixed in 1.3
          Hide
          leedega Kevin Phillips added a comment -

          I'm not certain but I think this bug has been re-introduced in a recent version of your plugin. I can reproduce the problem using v1.5.3 on Jenkins LTS core v2.46.3.

          From what I can tell the value of the referenced parameter always receives the same value as it had by default when the build page loads initially. So if the check box is checked by default, the parameter always receives the value of "on" regardless of whether the box is checked or not by the user, and vice versa.

           

          Show
          leedega Kevin Phillips added a comment - I'm not certain but I think this bug has been re-introduced in a recent version of your plugin. I can reproduce the problem using v1.5.3 on Jenkins LTS core v2.46.3. From what I can tell the value of the referenced parameter always receives the same value as it had by default when the build page loads initially. So if the check box is checked by default, the parameter always receives the value of "on" regardless of whether the box is checked or not by the user, and vice versa.  

            People

            Assignee:
            kinow Bruno P. Kinoshita
            Reporter:
            gils Gil Shinar
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated: