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

Not able to see parameters in "build with the parameters" option and blank error page after appling new changes

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • active-choices-plugin
    • None
    • Jenkins v1.415, Active Choices Plug-in v2.7

      Hi,

       

      I tried to build my job today but I was not able to see the parameters which were visible 2 days back.

       

      Also facing issue while applying changes to configuration of job. Getting blank error page.

      I have updated Jenkins to latest version 1.415 and Active choice parameter is also updated.

       

        1. Error.JPG
          Error.JPG
          33 kB
        2. image-2023-07-27-15-39-26-850.png
          image-2023-07-27-15-39-26-850.png
          18 kB
        3. image-2023-07-28-13-25-24-600.png
          image-2023-07-28-13-25-24-600.png
          20 kB
        4. Parameter.JPG
          Parameter.JPG
          15 kB
        5. Screenshot 2023-07-28 133010.png
          Screenshot 2023-07-28 133010.png
          53 kB
        6. Screenshot 2023-07-28 133010-2.png
          Screenshot 2023-07-28 133010-2.png
          53 kB

          [JENKINS-71706] Not able to see parameters in "build with the parameters" option and blank error page after appling new changes

          Trevor Major added a comment - - edited

          We are also experiencing issues with parameters no longer appearing.

          Fix was to downgrade the Active Choices Plug-in back to version 2.65.

           

          Jenkins:   2.401.2 LTS
          Active Choices Plug-in:  2.7

           

          Pipeline code:

          separator(name: "ENV_CHOICE", sectionHeader: "IAC Environment"),
                            choice(choices: "\n${cmn.listToChoices(cmn.currentAllowedTargetEnvs())}", name: 'targetEnv', description: 'Environment to deploy updates'),
                            [$class: 'CascadeChoiceParameter', choiceType: 'PT_SINGLE_SELECT', name: 'masterConfEnv', referencedParameters: 'targetEnv',
                                script:
                                    [$class: 'GroovyScript', fallbackScript: [classpath: [], script: "return []"],
                                    script: [classpath: [], sandbox: true, script: cmn.activeChoicesEnvsToMastersScript(cmn.currentAllowedTargetEnvs(),cmn.currentAllowedTargetEnvs(),'targetEnv',false,true) ]
                                ]
                            ],

           

          Error:

           

          Trevor Major added a comment - - edited We are also experiencing issues with parameters no longer appearing. Fix was to downgrade the Active Choices Plug-in back to version 2.65.   Jenkins:   2.401.2 LTS Active Choices Plug-in:  2.7   Pipeline code: separator(name: "ENV_CHOICE" , sectionHeader: "IAC Environment" ),                             choice(choices: "\n${cmn.listToChoices(cmn.currentAllowedTargetEnvs())}" , name: 'targetEnv' , description: 'Environment to deploy updates' ),                             [$class: 'CascadeChoiceParameter' , choiceType: 'PT_SINGLE_SELECT' , name: 'masterConfEnv' , referencedParameters: 'targetEnv' ,                                 script:                                     [$class: 'GroovyScript' , fallbackScript: [classpath: [], script: " return []" ],                                     script: [classpath: [], sandbox: true , script: cmn.activeChoicesEnvsToMastersScript(cmn.currentAllowedTargetEnvs(),cmn.currentAllowedTargetEnvs(), 'targetEnv' , false , true ) ]                                 ]                             ],   Error:  

          Amol added a comment - - edited

          Hi tmajor 

          Thnak you for looking into this.

          I tried with downgrading the Active Choices Plug-in to version 2.6.5, but the issue is still present.

          Amol added a comment - - edited Hi tmajor   Thnak you for looking into this. I tried with downgrading the Active Choices Plug-in to version 2.6.5, but the issue is still present .

          Amol added a comment -

          Resolved. 

          Apparently the incorrect implementation of CSP headers is the cause of this issue.
           

          Amol added a comment - Resolved.  Apparently the incorrect implementation of CSP headers is the cause of this issue.  

            kinow Bruno P. Kinoshita
            amolmali5 Amol
            Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: