[JIRA] (JENKINS-41662) Proceed button fails (investigate)
Title: Message Title
Lukas Kallies edited a comment on JENKINS-41662
Re: Proceed button fails (investigate)
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
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178489.1486047513000.15581.1587542700616%40Atlassian.JIRA.
[JIRA] (JENKINS-41662) Proceed button fails (investigate)
Title: Message Title
Lukas Kallies edited a comment on JENKINS-41662
Re: Proceed button fails (investigate)
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}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178489.1486047513000.15543.1587541680593%40Atlassian.JIRA.
[JIRA] (JENKINS-41662) Proceed button fails (investigate)
Title: Message Title
Lukas Kallies commented on JENKINS-41662
Re: Proceed button fails (investigate)
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'
}
}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178489.1486047513000.15522.1587541620533%40Atlassian.JIRA.
[JIRA] (JENKINS-41662) Proceed button fails (investigate)
Title: Message Title Christian Ciach commented on JENKINS-41662 Re: Proceed button fails (investigate) 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. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178489.1486047513000.6869.1586172360701%40Atlassian.JIRA.
[JIRA] (JENKINS-41662) Proceed button fails (investigate)
Title: Message Title
Jim Yanko edited a comment on JENKINS-41662
Re: Proceed button fails (investigate)
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.0Saw 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:///job//job//job///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.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit
[JIRA] (JENKINS-41662) Proceed button fails (investigate)
Title: Message Title Jim Yanko commented on JENKINS-41662 Re: Proceed button fails (investigate) 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:///job//job//job///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. Add Comment
[JIRA] (JENKINS-41662) Proceed button fails (investigate)
Title: Message Title Angelo Loria commented on JENKINS-41662 Re: Proceed button fails (investigate) Also seeing this. Jenkins ver. 2.190.1 Blue Ocean 1.21.0 Clicking proceed results in this- Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178489.1486047513000.8208.1579018321708%40Atlassian.JIRA.
[JIRA] (JENKINS-41662) Proceed button fails (investigate)
Title: Message Title Angelo Loria updated an issue Jenkins / JENKINS-41662 Proceed button fails (investigate) Change By: Angelo Loria Attachment: image-2020-01-14-10-11-16-669.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178489.1486047513000.8191.1579018321294%40Atlassian.JIRA.
[JIRA] (JENKINS-41662) Proceed button fails (investigate)
Title: Message Title Angelo Loria updated an issue Jenkins / JENKINS-41662 Proceed button fails (investigate) Change By: Angelo Loria Attachment: screenshot-1.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178489.1486047513000.8174.1579018260851%40Atlassian.JIRA.
[JIRA] (JENKINS-41662) Proceed button fails (investigate)
Title: Message Title Ted Sanders commented on JENKINS-41662 Re: Proceed button fails (investigate) 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. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-41662) Proceed button fails (investigate)
Title: Message Title Tim Huang commented on JENKINS-41662 Re: Proceed button fails (investigate) also having this issue... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178489.1486047513000.2067.1564170420488%40Atlassian.JIRA.
[JIRA] (JENKINS-41662) Proceed button fails (investigate)
Title: Message Title Andrii Rymar commented on JENKINS-41662 Re: Proceed button fails (investigate) 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)" Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178489.1486047513000.11846.1563270360343%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41662) Proceed button fails (investigate)
Title: Message Title Andrei Muresianu commented on JENKINS-41662 Re: Proceed button fails (investigate) 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. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41662) Proceed button fails (investigate)
Title: Message Title Dmitry Chernivetsky commented on JENKINS-41662 Re: Proceed button fails (investigate) i can reroduce this issue. jenkins version 2.150.1 blueocean plugin 1.9.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41662) Proceed button fails (investigate)
Title: Message Title
Dhiraj Baheti edited a comment on JENKINS-41662
Re: Proceed button fails (investigate)
@[~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.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41662) Proceed button fails (investigate)
Title: Message Title
Dhiraj Baheti edited a comment on JENKINS-41662
Re: Proceed button fails (investigate)
@[~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.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41662) Proceed button fails (investigate)
Title: Message Title
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 / JENKINS-41662
Proceed button fails (investigate)
Change By:
Dhiraj Baheti
Resolution:
Fixed
Status:
Closed Reopened
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-41662) Proceed button fails (investigate)
Title: Message Title Paul Kramer updated an issue Jenkins / JENKINS-41662 Proceed button fails (investigate) Change By: Paul Kramer Attachment: image-2018-08-10-13-33-42-164.png Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41662) Proceed button fails (investigate)
Title: Message Title Paul Kramer edited a comment on JENKINS-41662 Re: Proceed button fails (investigate) 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? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41662) Proceed button fails (investigate)
Title: Message Title Paul Kramer updated an issue Jenkins / JENKINS-41662 Proceed button fails (investigate) Change By: Paul Kramer Attachment: image-2018-08-10-13-35-50-968.png Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41662) Proceed button fails (investigate)
Title: Message Title Paul Kramer commented on JENKINS-41662 Re: Proceed button fails (investigate) We see the same behavior. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41662) Proceed button fails (investigate)
Title: Message Title Paul Kramer updated an issue Jenkins / JENKINS-41662 Proceed button fails (investigate) Change By: Paul Kramer Comment: HowdyWe see this too.!image-2018-08-10-13-33-42-164.png! Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41662) Proceed button fails (investigate)
Title: Message Title Paul Kramer commented on JENKINS-41662 Re: Proceed button fails (investigate) Howdy We see this too. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41662) Proceed button fails (investigate)
Title: Message Title Paul Kramer updated an issue Jenkins / JENKINS-41662 Proceed button fails (investigate) Change By: Paul Kramer Attachment: image-2018-08-10-13-33-42-164.png Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41662) Proceed button fails (investigate)
Title: Message Title Michael Neale commented on JENKINS-41662 Re: Proceed button fails (investigate) 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. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41662) Proceed button fails (investigate)
Title: Message Title Tom FENNELLY updated JENKINS-41662 Jenkins / JENKINS-41662 Proceed button fails (investigate) Change By: Tom FENNELLY Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41662) Proceed button fails (investigate)
Title: Message Title Tom FENNELLY commented on JENKINS-41662 Re: Proceed button fails (investigate) 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. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41662) Proceed button fails (investigate)
Title: Message Title Tom FENNELLY updated JENKINS-41662 Jenkins / JENKINS-41662 Proceed button fails (investigate) Change By: Tom FENNELLY Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41662) Proceed button fails (investigate)
Title: Message Title Tom FENNELLY started work on JENKINS-41662 Change By: Tom FENNELLY Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41662) Proceed button fails (investigate)
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-41662 Proceed button fails (investigate) Change By: Michael Neale Summary: Proceed button fails (investigate) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
