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

Blueocean paused for Input requested, but never asks for it

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Blocker Blocker
    • blueocean-plugin
    • None

      To put simply we have a few jobs that we start from "blueocean" view.

      The job starts fine and moves onto "asking fro user input"

      The step will show the lines:

      [Pipeline] input 
      Input requested

      But nothing is ever requested... If we switch to the "old UI" we can see the left link to provide input or do so from the console it self.

          [JENKINS-51050] Blueocean paused for Input requested, but never asks for it

          James Dumay added a comment -

          miguelc could you please post a simplified example Jenkinsfile that demonstrates this problem?

          cc jbriden

          James Dumay added a comment - miguelc could you please post a simplified example Jenkinsfile that demonstrates this problem? cc jbriden

          Mykola Ulianytskyi added a comment - - edited

          Hello

          I have the same issue on Jenkins 2.121.1.

          Sample pipeline:

          node {
              params = input(parameters: [
                  booleanParam(name: 'param1')
              ])
          
              stage('build') {
                  echo("${params}")
              }
          }
          

          Please fix this bug.

          Thank you

          Mykola Ulianytskyi added a comment - - edited Hello I have the same issue on Jenkins 2.121.1. Sample pipeline: node { params = input(parameters: [ booleanParam(name: 'param1' ) ]) stage( 'build' ) { echo( "${params}" ) } } Please fix this bug. Thank you

          Miguel C added a comment -

          In my case this seemed to have been related to the position where I was putting the input, I need to ask different input based on different values of a parameter and so I had a switch case for this outside of the node block, this seems to cause problems with blueocean.

          It now works after making sure any input blocks are inside the node block, I still face one issue though.

          The Proceed button takes to long to do any action, and seems that nothing is happening which leads people to press on it again and again see: https://issues.jenkins-ci.org/browse/JENKINS-41662?focusedCommentId=342792&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-342792

          Miguel C added a comment - In my case this seemed to have been related to the position where I was putting the input, I need to ask different input based on different values of a parameter and so I had a switch case for this outside  of the node block, this seems to cause problems with blueocean. It now works after making sure any input blocks are inside the node block, I still face one issue though. The Proceed button takes to long to do any action, and seems that nothing is happening which leads people to press on it again and again see: https://issues.jenkins-ci.org/browse/JENKINS-41662?focusedCommentId=342792&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-342792

          Miguel C added a comment -

          any news on this? it still happens using scripted pipeline, and the doc is not clear about places where we shouldn't be using this so it plays nice with blueocean (and even so I would consider it a bug since the classic ui works just fine)

          Miguel C added a comment - any news on this? it still happens using scripted pipeline, and the doc is not clear about places where we shouldn't be using this so it plays nice with blueocean (and even so I would consider it a bug since the classic ui works just fine)

          Sebastien Guery added a comment - - edited

          Same bug for me:

          def doPipeline = false
          try{
              doDeploy = input(message: 'Do you want to do the pipeline?', ok: 'Submit',
                          parameters: [[$class: 'BooleanParameterDefinition', defaultValue: false, description: 'Click on the checkbox to do the pipeline. Then click on "Submit" button',name: 'Do the pipeline']])
          } catch(err) { 
              doPipeline = false
              echo "Pipeline aborted by user."
          }
          node
          {
              echo "doPipline value = ${doPipeline}"
              stage('build'){
                  echo "Stage build..."
              }
          }
          
          

          Jenkins ver. 2.190.3

          Sometimes the input requested form is displayed and sometimes not on rerun with the same pipeline. It depends if I click on abort or submit and then rerun.

           

          Could you fix this bug?

           

          Regards

           

           

          Sebastien Guery added a comment - - edited Same bug for me: def doPipeline = false try { doDeploy = input(message: 'Do you want to do the pipeline?' , ok: 'Submit' , parameters: [[$class: 'BooleanParameterDefinition' , defaultValue: false , description: 'Click on the checkbox to do the pipeline. Then click on "Submit" button' ,name: 'Do the pipeline' ]]) } catch (err) { doPipeline = false echo "Pipeline aborted by user." } node { echo "doPipline value = ${doPipeline}" stage( 'build' ){ echo "Stage build..." } } Jenkins ver. 2.190.3 Sometimes the input requested form is displayed and sometimes not on rerun with the same pipeline. It depends if I click on abort or submit and then rerun.   Could you fix this bug?   Regards    

            Unassigned Unassigned
            miguelc Miguel C
            Votes:
            3 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated: