-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
-
pipeline 1.13
jenkins 1.642.1
In the event a pipeline build will not die you can hard kill it - however hard killing it will leave the JVMs CPS thread still running on the master.
e.g. with the script
def spin() { while (true) {} } def map = [:] map ["spin_it"] = { spin() } } parallel map
you will need to hard kill it to stop it (on windows at least) - but inspecting the JVM threads you can see the CPS thread is still running in a tight loop.
A hard kill should probably (if it is safe without causing deadlocks elsewhere) brutally kill the thread as well. After a while you may run out of handles or other native resources due to the thread usage, meaning you need to restart Jenkins to get it working again.
- is blocking
-
JENKINS-25550 Hard kill
- Resolved
- is related to
-
JENKINS-25623 timeout step should be able to kill infinite loop
- Resolved
-
JENKINS-45772 Build cannot be aborted when plugin is in waitUntilContainerIsReady
- Open
-
JENKINS-31484 Endless loop in DefaultInvoker.getProperty when accessing field via getter/setter without @
- Resolved
-
JENKINS-37719 Build cannot be interrupted if `docker stop` hangs
- Resolved
-
JENKINS-30978 URLConnection.content.text hangs
- Resolved
-
JENKINS-32228 Event when timeout is reach should be customizable
- Resolved
- relates to
-
JENKINS-43276 CoreWrapperStep should run SimpleBuildWrapper.setUp asynchronously
- Resolved
-
JENKINS-47006 durable-task's BourneShellScript.launchWithCookie trips workflow-cps-plugin's 5-minute timeout
- Resolved
-
JENKINS-44785 Add Built-in Request timeout support in Remoting
- Open
-
JENKINS-42561 Users should be able to custom configure the timeout on pipeline build wrappers/steps
- Resolved
- links to