Details
-
Bug
-
Status: Open (View Workflow)
-
Minor
-
Resolution: Unresolved
-
None
-
Jenkins: 2.259
Lockable resources plugin: 2.10
Pipeline Input Step: 2.12
Description
After restart, having input step inside lock and several jobs waiting to acquire the lock, not able to Proceed or Abort anymore.
Steps to reproduce:
1) Have "input" inside a lock block
2) Start several build of the same job (the earliest will block on "input" and others block on "lock")
3) Restart Jenkins
Observed behaviour:
Can not Proceed or Abort the build with buttons anymore. Even generic abort button does not work for the build, have to "kill" it.
Expected behaviour:
One can Proceed or Abort the build.
Minimal pipeline to reproduce:
pipeline { agent none stages { stage('a') { steps { lock('lock-me-in') { script { input 'Are you okay?' } } } } } }
Output in the jenkins log:
WARNING org.jenkinsci.plugins.workflow.support.steps.input.InputAction: no flow execution found for input-simple #8
Attachments
Issue Links
- is related to
-
JENKINS-44855 input leaves build hanging - input.InputAction loadExecutions no flow execution found
-
- Open
-
-
JENKINS-37998 Warning log "no flow execution found for pipelinejob #1"
-
- Open
-
Activity
Field | Original Value | New Value |
---|---|---|
Description |
After restart, having input step inside lock and several jobs waiting to acquire the lock, not able anymore to Proceed or Abort. Steps to reproduce: 1) Have "input" inside a lock block 2) Start several build of the same job (the earliest will block on "input" and others block on "lock") 3) Restart Jenkins Observed behaviour: Can not Proceed or Abort the build with buttons anymore. Even generic abort button does not work for the build, have to "kill" it. Expected behaviour: One can Proceed or Abort the build. Minimal pipeline to reproduce: {noformat} pipeline { agent none stages { stage('a') { steps { lock('lock-me-in') { script { input 'Are you okay?' } } } } } } {noformat} Output in the jenkins log: {noformat} WARNING org.jenkinsci.plugins.workflow.support.steps.input.InputAction: no flow execution found for input-simple #8 {noformat} |
After restart, having input step inside lock and several jobs waiting to acquire the lock, not able to Proceed or Abort anymore. Steps to reproduce: 1) Have "input" inside a lock block 2) Start several build of the same job (the earliest will block on "input" and others block on "lock") 3) Restart Jenkins Observed behaviour: Can not Proceed or Abort the build with buttons anymore. Even generic abort button does not work for the build, have to "kill" it. Expected behaviour: One can Proceed or Abort the build. Minimal pipeline to reproduce: {noformat} pipeline { agent none stages { stage('a') { steps { lock('lock-me-in') { script { input 'Are you okay?' } } } } } } {noformat} Output in the jenkins log: {noformat} WARNING org.jenkinsci.plugins.workflow.support.steps.input.InputAction: no flow execution found for input-simple #8 {noformat} |
Assignee | Tobias Gruetzmacher [ tgr ] |
Link | This issue is related to JENKINS-37998 [ JENKINS-37998 ] |
Link | This issue is related to JENKINS-44855 [ JENKINS-44855 ] |