Details
-
Bug
-
Status: Resolved (View Workflow)
-
Critical
-
Resolution: Fixed
-
None
-
-
workflow-cps 2.66
Description
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.
Attachments
Issue Links
- 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
I was hoping that my proposed fix of
JENKINS-41854would 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