[JIRA] (JENKINS-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title Jesse Glick updated JENKINS-41791 Jenkins / JENKINS-41791 Pipeline waiting for user input does not survive Jenkins restart Change By: Jesse Glick Status: In Progress Review 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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title Jesse Glick started work on JENKINS-41791 Change By: Jesse Glick Status: Open In Progress 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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-41791 Pipeline waiting for user input does not survive Jenkins restart Change By: Jesse Glick Assignee: Jesse Glick 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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title Jesse Glick commented on JENKINS-41791 Re: Pipeline waiting for user input does not survive Jenkins restart JENKINS-53709 was a similar 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title Jesse Glick commented on JENKINS-41791 Re: Pipeline waiting for user input does not survive Jenkins restart Digging into the program state confirms that all kinds of stuff including the ContainerExecDecorator is still there even after the container step exited. Seems like a bug in ParallelStep. 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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title Jesse Glick commented on JENKINS-41791 Re: Pipeline waiting for user input does not survive Jenkins restart I was hoping that my proposed fix of JENKINS-41854 would solve the symptom in at least some cases, by allowing a PickleDynamicContext to be saved in program.dat rather than the actual FilePath in a DryCapsule. Unfortunately it does not seem to work—something is apparently still trying to rehydrate the bogus pickle—though at least the override of TryRepeatedly.getOwner from FilePathPickle makes the problem a bit more apparent, as the resumed build will repeatedly print Still trying to load Looking for path named ‘/home/jenkins/workspace/workaround’ on computer named ‘jenkins-input-repro-48e88ac1-40ab-4d74-9ba2-1f25e728be3c--3h6s8’ 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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title Tim Myers commented on JENKINS-41791 Re: Pipeline waiting for user input does not survive Jenkins restart Haha awesome, well maybe I can workaround for now by just removing any usage or parallel. I'll give that a shot on the actual workflow. 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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-41791 Pipeline waiting for user input does not survive Jenkins restart Removing the parallel step and running the same sh steps sequentially does work around the issue, confirming that on top of everything else there is a serial form leak bug in workflow-cps. Change By: Jesse Glick Component/s: workflow-cps-plugin 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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title
Tim Myers edited a comment on JENKINS-41791
Re: Pipeline waiting for user input does not survive Jenkins restart
{{ Hmm interesting. My pods have definitely been destroying and recreating anew for each {{node { () }} } scope block, whether that's expected/intended or not.. As you said though, that could well be related to the bug. }}
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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title
Tim Myers edited a comment on JENKINS-41791
Re: Pipeline waiting for user input does not survive Jenkins restart
{{Hmm interesting. My pods have definitely been destroying and recreating anew for each {{ node{} }} scope block, whether that's expected/intended or not.. As you said though, that could well be related to the bug.}}
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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title
Tim Myers edited a comment on JENKINS-41791
Re: Pipeline waiting for user input does not survive Jenkins restart
{{ Hmm interesting. My pods have definitely been destroying and recreating anew for each ` node{} ` scope block, whether that's expected/intended or not.. As you said though, that could well be related to the bug. }}
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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title
Tim Myers commented on JENKINS-41791
Re: Pipeline waiting for user input does not survive Jenkins restart
Hmm interesting. My pods have definitely been destroying and recreating anew for each `node{}` scope block, whether that's expected/intended or not.. As you said though, that could well be related to the bug.
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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title
Jesse Glick commented on JENKINS-41791
Re: Pipeline waiting for user input does not survive Jenkins restart
I had assumed that a workaround in this case would be to actually release the pod before pausing the input (as you ought to do anyway):
def endToEndTests(target) {
stage('End to end tests') {
container('ci') {
parallel '1': {
sh 'sleep 10'
}, '2': {
sh 'sleep 10'
}, '3': {
sh 'sleep 10'
}
}
}
}
def deploy(target) {
stage("Deploy to ${target}") {
container('ci') {
sh 'sleep 10'
}
}
}
def everything(target) {
def label = "jenkins-input-repro-${UUID.randomUUID().toString()}"
podTemplate(label: label, podRetention: onFailure(), activeDeadlineSeconds: 600, yaml: '''
apiVersion: v1
kind: Pod
spec:
containers:
- name: ci
image: golang:latest
tty: true
''') {
node(label) {
deploy(target)
endToEndTests(target)
}
}
}
everything 'staging'
stage('Approve prod') {
input message: 'Deploy to prod?'
}
everything 'prod'
Unfortunately it does not seem to work. The virtual thread dump shows that the program load is trying to deserialize a FilePath from jenkins-input-repro-390fc568-acbd-434d-9083-8de662760e28-khwqp, while the currently active agent is named jenkins-input-repro-390fc568-acbd-434d-9083-8de662760e28-5l5jr. Why the kubernetes plugin is reconstructing this agent, I have no idea (it should have been deleted as soon as the first node block exited, and in fact the second agent does disconnect on its own after a while); but that is less important than the fact that program.dat includes a FilePathPickle for a node block which has already closed.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-41791 Pipeline waiting for user input does not survive Jenkins restart Change By: Jesse Glick Component/s: kubernetes-plugin Component/s: pipeline-input-step-plugin Component/s: pipeline-stage-view-plugin 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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title
Jesse Glick commented on JENKINS-41791
Re: Pipeline waiting for user input does not survive Jenkins restart
The pod does actually go away though outside of the node blocks.
Not in my experience, although I did see it get killed later for unknown reasons. Not sure if that is related to the bug. Finally managed to reproduce. FTR:
Run Microk8s.
Run: java -Dhudson.Main.development=true -jar jenkins-war-2.164.1.war --prefix=/jenkins --httpPort=8090 --httpListenAddress=10.1.1.1
Load Jenkins via http://10.1.1.1:8090/jenkins/ which should also set its default URL (needed by the Kubernetes jnlp container callback).
Install {blueocean}}, pipeline-stage-view, and kubernetes plugins.
Add a Kubernetes cloud (no further configuration needed).
Create a Pipeline job based on yours but with that stuff uncommented, and with the resources section removed, to wit:
def label = "jenkins-input-repro-${UUID.randomUUID().toString()}"
def scmVars;
def endToEndTests(target) {
stage('End to end tests') {
container('ci') {
parallel '1': {
sh 'sleep 10'
}, '2': {
sh 'sleep 10'
}, '3': {
sh 'sleep 10'
}
}
}
}
def deploy(target) {
stage("Deploy to ${target}") {
container('ci') {
sh 'sleep 10'
}
}
}
podTemplate(label: label, podRetention: onFailure(), activeDeadlineSeconds: 600, yaml: """
apiVersion: v1
kind: Pod
spec:
containers:
- name: ci
image: golang:latest
tty: true
"""
) {
node(label) {
this.deploy('staging')
this.endToEndTests('staging')
}
stage('Approve prod') {
input message: 'Deploy to prod?'
}
node(label) {
this.deploy('prod')
this.endToEndTests('prod')
}
}
Start a build.
Wait for it to get to approval.
/safeRestart
When Jenkins comes back up, try to Proceed.
Not sure exactly how the endToEndTests plays into this, but anyway compared to the passing case, there is no Ready to run at … message, http://10.1.1.1:8090/jenkins/job/p/1/threadDump/ displays
Program is not yet loaded
Looking for path named ‘/home/jenkins/workspace/p’ on computer named ‘jenkins-input-repro-15556b06-275f-494f-84d3-4ba9c006f0c1--8b27g’
[JIRA] (JENKINS-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title Tim Myers commented on JENKINS-41791 Re: Pipeline waiting for user input does not survive Jenkins restart Possibly only with kubernetes, haven't tried otherwise. The pod does actually go away though outside of the node blocks. It doesn't hang around while waiting on input. 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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title Jesse Glick commented on JENKINS-41791 Re: Pipeline waiting for user input does not survive Jenkins restart So does this happen only when using the kubernetes plugin? (I will set aside the advice that an input step ought not be used inside podTemplate, as it forces the pod to stick around while waiting for a human to come back from vacation or whatever.) Anyway, I will see if I am able to reproduce locally. 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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title Tim Myers commented on JENKINS-41791 Re: Pipeline waiting for user input does not survive Jenkins restart Thanks, I was able to get tests running (took a bit as I'm not familiar with Java tooling). I am still trying to get a unit test that replicates the failure, however in the meantime, here is a fairly minimal Jenkinsfile of some interest: https://gist.github.com/timmyers/bcdcecce1095e5e4d94bc39d9bdcf018 As is, there are no issues. If I uncomment the `endToEndTests` lines though, the error occurs. Seems very odd to me. 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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title Jesse Glick commented on JENKINS-41791 Re: Pipeline waiting for user input does not survive Jenkins restart mvn test -Dtest=InputStepRestartTest\#whatever if you do not have anything better in your IDE. 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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title Tim Myers commented on JENKINS-41791 Re: Pipeline waiting for user input does not survive Jenkins restart I feel like I may be on to something. I think I have narrowed down to a fairly specific addition to my pipeline that seems to trigger the issue (at least in my case). Re: tests, is there any documentation how to run them locally for the `pipeline-input-step-plugin` repo. Or is the best bet to open a PR and let the CI run them for me? 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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title
Jesse Glick commented on JENKINS-41791
Re: Pipeline waiting for user input does not survive Jenkins restart
It should go without saying that a bug report with a minimal, self-contained, reproducible test case is far more likely to be addressed. For the more adventurous, we also welcome pull requests contributing a test case demonstrating the bug like
@Ignore("TODO times out at line such-and-such after printing such-and-such warning")
@Issue("JENKINS-41791")
@Test public void whatever() {…}
which in this case would presumably live in InputStepRestartTest. Such a PR is eligible for immediate merge, with a future fix ideally just deleting the @Ignore in the same commit.
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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title
Tim Myers commented on JENKINS-41791
Re: Pipeline waiting for user input does not survive Jenkins restart
Okay I'll see what I can come up with, thanks. I have one simple Jenkinsfile that seems to be immune, and one more complicated one that it occurs with. Both do very similar things, have no `input`s in have `node{}`, very odd. I'll see if I can come up with a minimal example that reproduces.
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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title
Tim Myers edited a comment on JENKINS-41791
Re: Pipeline waiting for user input does not survive Jenkins restart
Okay I'll see what I can come up with, thanks. I have one simple Jenkinsfile that seems to be immune, and one more complicated one that it occurs with. Both do very similar things, have no `input`s in have `node{}`, very odd.I'll see if I can come up with a minimal example that reproduces.
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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title Jesse Glick commented on JENKINS-41791 Re: Pipeline waiting for user input does not survive Jenkins restart Tim Myers no, it should not. If the situation described here happens, it is a bug. If we have a way to reproduce it from scratch, we can investigate a fix. 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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title
Tim Myers commented on JENKINS-41791
Re: Pipeline waiting for user input does not survive Jenkins restart
Jesse Glick Sam Van Oort Is this something that requires https://github.com/jenkinsci/pipeline-input-step-plugin/pull/3 to truly fix? I am running into the issue with `input` steps, using the kubernetes plugin. Pipelines that are currently waiting when the master is restarted become broken, unable to continue. This also affects being able to even load any blue ocean view which references the broken jobs. I have made sure that all of the `input` steps are not in `node{}` blocks, but the issue seems to still occur.
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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title Jeremy Mathevet commented on JENKINS-41791 Re: Pipeline waiting for user input does not survive Jenkins restart Same issue here, JENKINS-47860 and JENKINS-41791 are being very annoying. 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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title Damien Puig commented on JENKINS-41791 Re: Pipeline waiting for user input does not survive Jenkins restart JENKINS-47860 and JENKINS-41791 are a big issue for us as well. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title Cédric Caron commented on JENKINS-41791 Re: Pipeline waiting for user input does not survive Jenkins restart We are facing the same issue. JENKINS-47860 and JENKINS-41791 currently make a CD pipeline based on Jenkins very brittle. Could those 2 bugs be moved to a higher level of criticity? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title Junpeng Luo commented on JENKINS-41791 Re: Pipeline waiting for user input does not survive Jenkins restart Same behavior as described. Can't reproduce that in local Jenkins but for us it happened every time after each restarts recently in our PROD Jenkins. With following logs for builds can't click input step. Mar 23, 2018 12:22:37 PM org.jenkinsci.plugins.workflow.support.steps.input.InputAction loadExecutions WARNING: no flow execution found for my-job #79 Jenkins version 2.73.2 Pipeline input step plugin version 2.8 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title Daniel Wilmer commented on JENKINS-41791 Re: Pipeline waiting for user input does not survive Jenkins restart I still could not figure out how it happens. It still happens occasionally, but it has nothing to do with jenkins restarts. Maybe the cause are plugin updates. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-41791 Pipeline waiting for user input does not survive Jenkins restart Change By: Andrew Bayer Component/s: pipeline-input-step-plugin Component/s: pipeline 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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title Daniel Wilmer created an issue Jenkins / JENKINS-41791 Pipeline waiting for user input does not survive Jenkins restart Issue Type: Bug Assignee: Unassigned Attachments: blue ocean.png, log.png, paused for input.png, pipeline view.png Components: pipeline Created: 2017/Feb/07 6:36 AM Priority: Minor Reporter: Daniel Wilmer I have a lot of Pipeline Jobs that are waiting for user input before deploying to production. It is quite normal, that pipelines are in this state for several days. After a Jenkins restart (e.g. because of a Jenkins Update) the Pipelines are still in running state, but the user input controls are missing. log pipeline view paused for input Paused for input is available, but the controls are missing. blue ocean Add Comment
