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

Proceed button fails (investigate)

    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
    • Similar Issues:
    • Epic Link:
    • Sprint:
      1.0

      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
            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.
            Hide
            andrew_rymar Andrii Rymar added a comment -

            Having the exact issue, it happens most of the time I use "input" step.

            Console reports: "TypeError: error.responseBody is undefined (jenkins-js-extension.js:95465:21)"

            Show
            andrew_rymar Andrii Rymar added a comment - Having the exact issue, it happens most of the time I use "input" step. Console reports: "TypeError: error.responseBody is undefined (jenkins-js-extension.js:95465:21)"
            Hide
            timethos Tim Huang added a comment -

            also having this issue...

            Show
            timethos Tim Huang added a comment - also having this issue...
            Hide
            ts3648 Ted Sanders added a comment -

            I am experiencing the same problem with war: 2.190.3 and 

            Rolling back to different plugin versions puts blue ocean into a worsened, unusable state.  No screen output.  

            Show
            ts3648 Ted Sanders added a comment - I am experiencing the same problem with war:  2.190.3  and  Blue Ocean 1.21.0   Pub-Sub "light" Bus 1.13 Rolling back to different plugin versions puts blue ocean into a worsened, unusable state.  No screen output.  
            Hide
            whatsdevops Angelo Loria added a comment -

            Also seeing this.
            Jenkins ver. 2.190.1
            Blue Ocean 1.21.0

            Clicking proceed results in this-

             

             

            Show
            whatsdevops Angelo Loria added a comment - Also seeing this. Jenkins ver. 2.190.1 Blue Ocean 1.21.0 Clicking proceed results in this-    

              People

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

                Dates

                • Created:
                  Updated: