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

Proceed button fails (investigate)

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Reopened (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: blueocean-plugin
    • Labels:
      None
    • Environment:
      jenkins 2.44
      blueocean-plugin 1.0.0-b21
    • Epic Link:
    • Sprint:
      1.0
    • Similar Issues:

      Description

      It seems under some conditions the proceed button for input does not work and the UI does not automatically update to reflect this state.

      There needs to be some manual testing around inputs to check if we are handling errors correctly and that the state of the UI is handled appropriately in error cases.

      It would be prudent to test around error cases and SSE updates for input here too.

      It would also be worth ensuring that under successful conditions that the UI updates correctly on proceeding with input.

      Original request
      Recently our inputs (with checkboxes) stopped to work. Pressing "Proceed" button does nothing, there is an error response:

      Error processing Input Submit request. This Run instance does not have an Input with an id of 'D875578491b444dd8bc3f26a12399d2a'.

      This occurs in ~90%, some success still may exist )

        Attachments

          Issue Links

            Activity

            Hide
            miguelc Miguel C added a comment -

            I'm facing a similar issue so I though I'de comment here instead of opening a new one...

            When pressing proceed it seems nothing is happening and we are tempted to press the button again, and get  `This Run instance does not have an Input with an id of "someID"` (I'm setting a fixed ID)

            If we refresh we noticed proceed did work the page just takes to long to move to the next view.

            I tried this with Chrome Dev tools open and it just seems that it takes a lot of time for something to happen, giving the impression that nothing was being done and so users tend to press proceed over and over again :/

            Show
            miguelc Miguel C added a comment - I'm facing a similar issue so I though I'de comment here instead of opening a new one... When pressing proceed it seems nothing is happening and we are tempted to press the button again, and get  `This Run instance does not have an Input with an id of "someID"` (I'm setting a fixed ID) If we refresh we noticed proceed did work the page just takes to long to move to the next view. I tried this with Chrome Dev tools open and it just seems that it takes a lot of time for something to happen, giving the impression that nothing was being done and so users tend to press proceed over and over again :/
            Hide
            dingerpk57 Paul Kramer added a comment - - edited

            We see the same behavior.


            We expect that pressing the Run button should take us to the page i show in the second part of this picture. We should see the input page. But we don't. We have to press refresh.

            Is there any thought on what we should investigate?

            Show
            dingerpk57 Paul Kramer added a comment - - edited We see the same behavior. We expect that pressing the Run button should take us to the page i show in the second part of this picture. We should see the input page. But we don't. We have to press refresh. Is there any thought on what we should investigate?
            Hide
            dhirajbaheti Dhiraj Baheti added a comment - - edited

            @Tom FENNELLY - I am still facing this issue while using interactive user input code as below -

            timeout(time: 60, unit: 'SECONDS')

            { QA_ACTION = input(id: 'qaAction', message: 'What do you want to do?', parameters: [[$class: 'ChoiceParameterDefinition', defaultValue: 'NA', description:'Select Any of below QA Activities', name:'qaActionChoice', choices: "Move To QA\nApprove Package\nDiscard Package"]]) }

            I am indeed using v1.9.0 version of Blue Ocean and above bug was fixed in older versions 15 months back(1.0.0-b25 (March 6th, 2017)). 

            The behavior is exactly similar as reported above. Proceed button works 10-15% times while no activity in rest of the cases and works if refreshed the page.

            I also verified the fix comments at https://github.com/jenkinsci/blueocean-plugin/pull/875

            and I am not passing null id and only one instance running at a time.

             

            Please suggest.

             

            Show
            dhirajbaheti Dhiraj Baheti added a comment - - edited @ Tom FENNELLY - I am still facing this issue while using interactive user input code as below - timeout(time: 60, unit: 'SECONDS') { QA_ACTION = input(id: 'qaAction', message: 'What do you want to do?', parameters: [[$class: 'ChoiceParameterDefinition', defaultValue: 'NA', description:'Select Any of below QA Activities', name:'qaActionChoice', choices: "Move To QA\nApprove Package\nDiscard Package"]]) } I am indeed using v1.9.0 version of Blue Ocean and above bug was fixed in older versions 15 months back(1.0.0-b25 (March 6th, 2017)).  The behavior is exactly similar as reported above. Proceed button works 10-15% times while no activity in rest of the cases and works if refreshed the page. I also verified the fix comments at https://github.com/jenkinsci/blueocean-plugin/pull/875 and I am not passing null id and only one instance running at a time.   Please suggest.  
            Hide
            dcherniv Dmitry Chernivetsky added a comment -

            i can reroduce this issue. jenkins version 2.150.1

            blueocean plugin 1.9.0

            Show
            dcherniv Dmitry Chernivetsky added a comment - i can reroduce this issue. jenkins version 2.150.1 blueocean plugin 1.9.0
            Hide
            andreimuresianu Andrei Muresianu added a comment -

            I am experiencing the same problem as reported above where after pressing the submit button the pipeline does not move on to the next stage unless I refresh the page.

            Show
            andreimuresianu Andrei Muresianu added a comment - I am experiencing the same problem as reported above where after pressing the submit button the pipeline does not move on to the next stage unless I refresh the page.

              People

              • Assignee:
                tfennelly Tom FENNELLY
                Reporter:
                kamikaze Oleg Korsak
              • Votes:
                6 Vote for this issue
                Watchers:
                12 Start watching this issue

                Dates

                • Created:
                  Updated: