-
Bug
-
Resolution: Fixed
-
Critical
-
None
-
-
workflow-cps 2.66
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.
paused for input
Paused for input is available, but the controls are missing.
- duplicates
-
JENKINS-37998 Warning log "no flow execution found for pipelinejob #1"
- Open
- relates to
-
JENKINS-41854 Contextualize a fresh FilePath after an agent reconnection
- Resolved
-
JENKINS-53709 Parallel blocks in node blocks cause executors to be persisted outside of the node block
- Resolved
-
JENKINS-63164 Closures in block-scoped steps can reference dead CpsBodyExecutions
- Resolved
-
JENKINS-39552 After restart, interrupted pipeline deadlocks waiting for executor
- Closed
- links to