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

In active choice parameter with groovy script, groovy sandbox checkbox gets unchecked after a build

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • active-choices-plugin
    • None
    • Jenkins 2.235.5
      Active Choices Plug-in 2.5.1

    Description

      I configured a job using Active Choice Parameter with Groovy Script. I did check "Use Groovy Sandbox" below the script and save.

      I was able to run a build after the initial configuration.

      But after that build, the "Use Groovy Sandbox" checkbox got wipe out and the parameter doesn't display correctly. I had to reconfigure and check that box but I am not able to run it once because it will get wiped out again.

      Attachments

        Activity

          Ascending order - Click to sort in descending order
          kinow Bruno P. Kinoshita added a comment -

          I was not able to reproduce it. I created a job with a single parameter and with a Groovy script with that checkbox checked.

          Reloaded configuration a couple times, and the checkbox was still checked.

          Executed the job twice, producing two succeeded builds. Checked the checkbox status in-executions, and after both builds were produced. The check box was always selected.

          Same plug-in version, only Jenkins version a bit older 2.204.1. Not sure if the Jenkins version could interfere; or perhaps the Scriptler version?

          If anybody else is able to reproduce in another environment, and if possible to share the config.xml of the job, then I will try it again.

          Thanks

          Bruno

          kinow Bruno P. Kinoshita added a comment - I was not able to reproduce it. I created a job with a single parameter and with a Groovy script with that checkbox checked. Reloaded configuration a couple times, and the checkbox was still checked. Executed the job twice, producing two succeeded builds. Checked the checkbox status in-executions, and after both builds were produced. The check box was always selected. Same plug-in version, only Jenkins version a bit older 2.204.1. Not sure if the Jenkins version could interfere; or perhaps the Scriptler version? If anybody else is able to reproduce in another environment, and if possible to share the config.xml of the job, then I will try it again. Thanks Bruno
          uskar Udayendu added a comment -

          Hi Bruno,

           

          I am using the same setup like Lu and getting the same issue.

          Every time when we are running the build, we are using "Build with Parameters" button and every time its not able to load the required parameters. 

          Then have to click on the Configure and select all the check boxes and save. After that only "Build with Parameters" button is able to load the required parameters.

           

          Thanks,

          Udayendu Kar

          uskar Udayendu added a comment - Hi Bruno,   I am using the same setup like Lu and getting the same issue. Every time when we are running the build, we are using " Build with Parameters " button and every time its not able to load the required parameters.  Then have to click on the Configure and select all the check boxes and save. After that only " Build with Parameters " button is able to load the required parameters.   Thanks, Udayendu Kar
          kinow Bruno P. Kinoshita added a comment -

          Thanks Udayendu. I will give it another try, this time with the exact versions, before trying to upgrade Jenkins/libs.

          kinow Bruno P. Kinoshita added a comment - Thanks Udayendu. I will give it another try, this time with the exact versions, before trying to upgrade Jenkins/libs.

          People

            kinow Bruno P. Kinoshita
            shen3lu4 Lu Shen
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: