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

hidden parameter type is not supported by Blue Ocean

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Hi all,

      I used to configure my jobs with parameters which I don´t want it been visible for the rest of my jenkins users so few months ago I decided to use the plugin "hidden parameter" for this case.

      The problem appears when I started to use Jenkins Pipelines with Blue Ocean. If I try to run a normal Pipeline (not declarative syntax) under Blue Ocean interface, I´m receiving the following error:

      "This pipeline uses input types that are unsupported. Use Jenkins Classic to resolve parametrized build."

      Seeing this link https://github.com/jenkinsci/blueocean-plugin/blob/d4a615534c8f8a5e94affc1a612038be90b109f9/blueocean-core-js/src/js/parameter/index.js#L20

      I don´t see the hidden parameter type like supported:

      Could be the hidden parameter type added to Blue Ocean?

      Many thanks to all!

        Attachments

          Activity

          Hide
          henrydobson Henry Dobson added a comment - - edited

          blue-ocean: 1.1.7

           

          The same error occurs when trying to use declarative pipeline for a file parameter.

          "This pipeline uses input types that are unsupported. Use Jenkins Classic to resolve parametrized build."

          Could support for file also be added?

            parameters {
              choice(name: 'Environment', choices: 'DEV\nQA\nSTAGE\nPROD', description: 'Which environment to import to.')
              file(name: 'import.json', description: 'The file to import.')
            }

          Show
          henrydobson Henry Dobson added a comment - - edited blue-ocean: 1.1.7   The same error occurs when trying to use declarative pipeline for a file parameter. "This pipeline uses input types that are unsupported. Use Jenkins Classic to resolve parametrized build." Could support for file also be added?   parameters {     choice(name: 'Environment', choices: 'DEV\nQA\nSTAGE\nPROD', description: 'Which environment to import to.')     file(name: 'import.json', description: 'The file to import.')   }
          Hide
          jamesdumay James Dumay added a comment -

          Henry have a search of JIRA. There is another blue ocean ticket that covers the file parameter

          Show
          jamesdumay James Dumay added a comment - Henry have a search of JIRA. There is another blue ocean ticket that covers the file parameter
          Hide
          henrydobson Henry Dobson added a comment -
          Show
          henrydobson Henry Dobson added a comment - James Dumay thanks  JENKINS-40395
          Hide
          pyrocks Mor L added a comment -

          I'm also facing the same error for the same reason. voted.

          Show
          pyrocks Mor L added a comment - I'm also facing the same error for the same reason. voted.
          Hide
          jhoblitt Joshua Hoblitt added a comment -

           I have been [re]using the same pipeline script for multiple, nearly identical jobs by using the job-dsl environmentVariables method to control script options.

          environmentVariables(
            WIPEOUT: false,
           )
          

          This works reasonably well but requires checking both env vars and params.* for script input. This isn't a major problem but it feels a bit "untidy" because there are two input mechanisms the script developer needs to mentally keep track of. Changing between a user set build parameter or fixed behavior would require either helper methods or pipeline script changes.

          Show
          jhoblitt Joshua Hoblitt added a comment -  I have been [re] using the same pipeline script for multiple, nearly identical jobs by using the job-dsl environmentVariables method to control script options. environmentVariables(   WIPEOUT: false , ) This works reasonably well but requires checking both env vars and params.* for script input. This isn't a major problem but it feels a bit "untidy" because there are two input mechanisms the script developer needs to mentally keep track of. Changing between a user set build parameter or fixed behavior would require either helper methods or pipeline script changes.
          Hide
          wistia_anders Anders Chen added a comment -

          I have a PR that resolves this issue here: https://github.com/jenkinsci/blueocean-plugin/pull/1721

          Show
          wistia_anders Anders Chen added a comment - I have a PR that resolves this issue here:  https://github.com/jenkinsci/blueocean-plugin/pull/1721
          Hide
          arpiatek Andrew Piatek added a comment -

          Did this get resolved?

          Anders, I see your PR is still open.

          Show
          arpiatek Andrew Piatek added a comment - Did this get resolved? Anders, I see your PR is still open.
          Hide
          daxroc Damien Roche added a comment -

          As the PR has been closed and not implemented - Has the suggestion from sophistifunk (list of inputs that can be ignored) been ticketed?
          https://github.com/jenkinsci/blueocean-plugin/pull/1721#issuecomment-383259538

          Show
          daxroc Damien Roche added a comment - As the PR has been closed and not implemented - Has the suggestion from sophistifunk (list of inputs that can be ignored) been ticketed? https://github.com/jenkinsci/blueocean-plugin/pull/1721#issuecomment-383259538

            People

            Assignee:
            jamesdumay James Dumay
            Reporter:
            majano Daniel Majano
            Votes:
            6 Vote for this issue
            Watchers:
            11 Start watching this issue

              Dates

              Created:
              Updated: