-
New Feature
-
Resolution: Fixed
-
Critical
Would be useful to have the equivalent of a SIGKILL for a WorkflowRun: immediately terminate the FlowExecution (with ABORTED), throw away all threads, and mark all StepContext as invalid. Would help in case regular interruption fails for whatever reason.
- depends on
-
JENKINS-28063 Triggering the same job twice results in zombie workflow run
- Resolved
-
JENKINS-28183 Hard killed job's stage blocks stage in following jobs
- Resolved
-
JENKINS-31841 Print stack trace to log before offering termination link
- Open
-
JENKINS-32986 hard killing a pipeline leaves the JVM CPS thread running.
- Open
-
JENKINS-33721 Hard kill links could be in the build sidepanel
- Resolved
- is blocking
-
JENKINS-31484 Endless loop in DefaultInvoker.getProperty when accessing field via getter/setter without @
- Resolved
-
JENKINS-26115 MultipleCompilationErrorsException leaves behind unkillable build
- Resolved
-
JENKINS-29413 Parallel with an empty map will run forever
- Resolved
-
JENKINS-26179 workflow job abort does not work if error in the syntax of the script
- Resolved
- is related to
-
JENKINS-29751 unkillable workflow builds with mansion cloud plugin
- Resolved
-
JENKINS-26105 Unkillable tasks
- Resolved
-
JENKINS-26106 Build of unconfigured flow cannot be killed
- Resolved
-
JENKINS-26130 Print progress of pending pickles
- Resolved
-
JENKINS-26363 Input step should permit cancellation from anyone with build abort permission
- Resolved
-
JENKINS-26709 A stage with concurrency: 0 creates a zombie workflow.
- Resolved
-
JENKINS-26148 Incorrect implementation of RetryStepExecution.stop
- Closed
-
JENKINS-28187 redefining "node" causes unrecoverable hang
- Closed
-
JENKINS-29705 Virtual thread dump
- Resolved
-
JENKINS-28189 Don't resume on restart
- Resolved
- links to