[JIRA] (JENKINS-41662) Proceed button fails (investigate)

Change By:	Michael Neale
Summary:	Proceed button fails (investigate)

This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)

tom.fennelly@gmail.com (JIRA)

unread,

Feb 28, 2017, 11:03:07 AM2/28/17

to jenkinsc...@googlegroups.com

Tom FENNELLY started work on

Change By:	Tom FENNELLY
Status:	Open In Progress

tom.fennelly@gmail.com (JIRA)

unread,

Mar 2, 2017, 8:17:04 AM3/2/17

to jenkinsc...@googlegroups.com

Tom FENNELLY updated

Jenkins /

Change By:	Tom FENNELLY
Status:	In Progress Review

tom.fennelly@gmail.com (JIRA)

unread,

Mar 2, 2017, 8:18:01 AM3/2/17

to jenkinsc...@googlegroups.com

Tom FENNELLY commented on

PR: https://github.com/jenkinsci/blueocean-plugin/pull/875

io.jenkins.blueocean.rest.impl.pipeline.InputStepImpl has some unusual code, resetting the ID of the underlying pipeline InputStep instance to a random ID. The result of this ... two browsers load the same input step ... the first browser is screwed because the id it is using to submit against no longer corresponds to a valid ID because the load from the second browser caused it to be changed via io.jenkins.blueocean.rest.impl.pipeline.InputStepImpl.

tom.fennelly@gmail.com (JIRA)

unread,

Mar 2, 2017, 8:21:05 AM3/2/17

to jenkinsc...@googlegroups.com

Tom FENNELLY commented on

I would have thought it was a total no-no for Blue Ocean code to be modifying underlying object model data in this way. The side effects of changes like this would surely have to be pretty bad.

tom.fennelly@gmail.com (JIRA)

unread,

Mar 2, 2017, 2:52:01 PM3/2/17

to jenkinsc...@googlegroups.com

Tom FENNELLY updated

Jenkins /

Change By:	Tom FENNELLY
Status:	In Review Resolved
Resolution:	Fixed

mneale@cloudbees.com (JIRA)

unread,

Mar 2, 2017, 3:53:03 PM3/2/17

to jenkinsc...@googlegroups.com

Michael Neale commented on

oh yes, this was a parallel problem as Tom FENNELLY found out.
Tom - not sure about that resetting of the ID or why - Vivek would know the story behind that if you ask him.

miguelmclara@gmail.com (JIRA)

unread,

Jun 28, 2018, 6:53:02 AM6/28/18

to jenkinsc...@googlegroups.com

Miguel C commented on

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 :/

This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)

pkramer@speakeasy.org (JIRA)

unread,

Aug 10, 2018, 4:34:03 PM8/10/18

to jenkinsc...@googlegroups.com

Paul Kramer updated an issue

Jenkins /

Change By:	Paul Kramer
Attachment:	image-2018-08-10-13-33-42-164.png

pkramer@speakeasy.org (JIRA)

unread,

Aug 10, 2018, 4:34:03 PM8/10/18

to jenkinsc...@googlegroups.com

Paul Kramer commented on

Howdy

We see this too.

pkramer@speakeasy.org (JIRA)

unread,

Aug 10, 2018, 4:35:02 PM8/10/18

to jenkinsc...@googlegroups.com

Paul Kramer updated an issue

Jenkins /

Change By:	Paul Kramer
Comment:

Howdy

We see this too.

!image-2018-08-10-13-33-42-164.png!

pkramer@speakeasy.org (JIRA)

unread,

Aug 10, 2018, 4:36:01 PM8/10/18

to jenkinsc...@googlegroups.com

Paul Kramer commented on

We see the same behavior.

pkramer@speakeasy.org (JIRA)

unread,

Aug 10, 2018, 4:36:01 PM8/10/18

to jenkinsc...@googlegroups.com

Paul Kramer updated an issue

Jenkins /

Change By:	Paul Kramer
Attachment:	image-2018-08-10-13-35-50-968.png

pkramer@speakeasy.org (JIRA)

unread,

Aug 10, 2018, 4:38:02 PM8/10/18

to jenkinsc...@googlegroups.com

Paul Kramer edited a comment on

We see the same behavior.

!image-2018-08-10-13-35-50-968.png!
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?

pkramer@speakeasy.org (JIRA)

unread,

Aug 10, 2018, 4:45:01 PM8/10/18

to jenkinsc...@googlegroups.com

Paul Kramer updated an issue

Jenkins /

Change By:	Paul Kramer
Attachment:	image-2018-08-10-13-33-42-164.png

dhirajbaheti@ymail.com (JIRA)

unread,

Nov 30, 2018, 1:08:03 AM11/30/18

to jenkinsc...@googlegroups.com

Dhiraj Baheti reopened an issue

@Tom FENNELLY - I am still facing this issue while using interactive user input 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.

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 no two people/instance running at a time.

Please suggest.

Jenkins /

Change By:	Dhiraj Baheti
Resolution:	Fixed
Status:	Closed Reopened

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

dhirajbaheti@ymail.com (JIRA)

unread,

Nov 30, 2018, 1:09:05 AM11/30/18

to jenkinsc...@googlegroups.com

Dhiraj Baheti edited a comment on

@[~tfennelly] - I am still facing this issue while using interactive user input 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.

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 no two people/ one instance running at a time.

Please suggest.

dhirajbaheti@ymail.com (JIRA)

unread,

Nov 30, 2018, 1:24:02 AM11/30/18

to jenkinsc...@googlegroups.com

Dhiraj Baheti edited a comment on

@[~tfennelly] - 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.

dcherniv@gmail.com (JIRA)

unread,

Dec 19, 2018, 9:08:02 PM12/19/18

to jenkinsc...@googlegroups.com

Dmitry Chernivetsky commented on

i can reroduce this issue. jenkins version 2.150.1

blueocean plugin 1.9.0

andreimuresianu1@gmail.com (JIRA)

unread,

Mar 22, 2019, 1:59:03 PM3/22/19

to jenkinsc...@googlegroups.com

Andrei Muresianu commented on

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.

andrew.rymar@gmail.com (JIRA)

unread,

Jul 16, 2019, 5:46:02 AM7/16/19

to jenkinsc...@googlegroups.com

Andrii Rymar commented on

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)"

tim@getethos.com (JIRA)

unread,

Jul 26, 2019, 3:47:02 PM7/26/19

to jenkinsc...@googlegroups.com

Tim Huang commented on

also having this issue...

ts3648@att.com (JIRA)

unread,

Jan 7, 2020, 10:05:02 AM1/7/20

to jenkinsc...@googlegroups.com

Ted Sanders commented on

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.

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

aloria@haworthmedia.com (JIRA)

unread,

Jan 14, 2020, 11:11:07 AM1/14/20

to jenkinsc...@googlegroups.com

Angelo Loria updated an issue

Jenkins /

Change By:	Angelo Loria
Attachment:	screenshot-1.png

aloria@haworthmedia.com (JIRA)

unread,

Jan 14, 2020, 11:12:07 AM1/14/20

to jenkinsc...@googlegroups.com

Angelo Loria updated an issue

Jenkins /

Change By:	Angelo Loria
Attachment:	image-2020-01-14-10-11-16-669.png

aloria@haworthmedia.com (JIRA)

unread,

Jan 14, 2020, 11:12:14 AM1/14/20

to jenkinsc...@googlegroups.com

Angelo Loria commented on

Also seeing this.
Jenkins ver. 2.190.1
Blue Ocean 1.21.0

Clicking proceed results in this-

jyanko@howlingduck.com (JIRA)

unread,

Jan 21, 2020, 4:54:07 PM1/21/20

to jenkinsc...@googlegroups.com

Jim Yanko commented on

Just saw this issue for the first time today on an instance maintained by my team.

Jenkins - CloudBees Jenkins Distribution 2.204.1.3-rolling
Blue Ocean - v1.21.0

Saw the same issue where first we got the message like

 
                                                                error processing input submit request...  
                                                            

Followed by subsequent attempts to submit the same input prompt giving us

 
                                                                JSON.parse: unexpected end of data at line 1 column 1 of the JSON data  
                                                            

The build does move on an actually do the rest of it's task and end up reporting successful

This warning appears to only show itself to the submitting user if they are using the BlueOcean UI rather than the Classic Jenkins views.

In our testing today, when we instead use one of the classic view UI for input...

direct input link: https://<hostname>/job/<folder>/job/<jobname>/job/<branchname>/<buildnumber>/input
hovering over the pending stag in classic pipeline view
clicking input link from within console log

...then the submission works fine without any visible errors/warnings and the job runs through to completion.

jyanko@howlingduck.com (JIRA)

unread,

Jan 21, 2020, 4:59:03 PM1/21/20

to jenkinsc...@googlegroups.com

Jim Yanko edited a comment on

Just saw this issue for the first time today on an instance maintained by my team.

* Jenkins - [CloudBees Jenkins Distribution 2.204.1.3-rolling|https://release-notes.cloudbees.com/product/CloudBees+Jenkins+Distribution]
* Blue Ocean - v1.21.0

Saw the same issue where first we got the message like

{code:java}
error processing input submit request... {code}

Followed by subsequent attempts to submit the same input prompt giving us

{code:java}
JSON.parse: unexpected end of data at line 1 column 1 of the JSON data {code}

The build does move on an actually do the rest of it's task and end up reporting successful

This warning appears to only show itself to the submitting user if they are using the BlueOcean UI rather than the Classic Jenkins views.

In our testing today, when we instead use one of the classic view UI for input...

* direct input link: {{ https://<hostname>/job/<folder>/job/<jobname>/job/<branchname>/<buildnumber>/input }}
* hovering over the pending stag stage in classic pipeline view
* clicking input link from within console log

...then the submission works fine without any visible errors/warnings and the job runs through to completion.

christian.ciach@gmail.com (JIRA)

unread,

Apr 6, 2020, 7:26:03 AM4/6/20

to jenkinsc...@googlegroups.com

Christian Ciach commented on

We are seeing the same issue with BlueOcean 1.22.0.

Do you guys use a reverse proxy? We are using Caddy 2 as a reverse proxy and i suspect that it could be the culprit.

This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)

kallies@puzzle-itc.de (JIRA)

unread,

Apr 22, 2020, 3:47:03 AM4/22/20

to jenkinsc...@googlegroups.com

Lukas Kallies commented on

We observed the same behaviour as Christian Ciach pointed out. We are using nginx as a reverse proxy. When not using the reverse proxy, we can use the input as expected.

Our input in Jenkinsfile is:

 
                                                                    stage('Deploy) {
      input {
        message 'Should we deploy to Satellite/Capsule?'
        ok 'Yes'
      }
      steps {
        echo 'deploying to Satellite/Capsules'
      }
    }
 
                                                            

kallies@puzzle-itc.de (JIRA)

unread,

Apr 22, 2020, 3:48:03 AM4/22/20

to jenkinsc...@googlegroups.com

Lukas Kallies edited a comment on

We observed the same behaviour as Christian Ciach [~christianciach] pointed out. We are using nginx as a reverse proxy. When not using the reverse proxy, we can use the input as expected.

Our input in Jenkinsfile is:

{code}

    stage('Deploy) {
      input {
        message 'Should we deploy to Satellite/Capsule?'
        ok 'Yes'
      }
      steps {
        echo 'deploying to Satellite/Capsules'
      }
    }

{code}

kallies@puzzle-itc.de (JIRA)

unread,

Apr 22, 2020, 4:05:03 AM4/22/20

to jenkinsc...@googlegroups.com

Lukas Kallies edited a comment on

We observed the same behaviour as [~christianciach] pointed out. We are using nginx as a reverse proxy. When not using the reverse proxy, we can use the input as expected.

Our input in Jenkinsfile is:

{code}
    stage('Deploy) {
      input {
        message 'Should we deploy to Satellite/Capsule?'
        ok 'Yes'
      }
      steps {
        echo 'deploying to Satellite/Capsules'
      }
    }
{code}

The issue was gone after we added Host, X-Forwarded-Proto and X-Forwarded-For Headers (before only X-Real-IP and X-Forwarded-Host). See e.g. https://wiki.jenkins.io/display/JENKINS/Jenkins+behind+an+NGinX+reverse+proxy