[JENKINS-34119] Shell process killed (OOM), but pipeline continues anyway

I have a jenkins pipeline, that invokes mvn with a 'sh mvn ....' invocation.

Occasionally, the output shows the maven execution suddenly stop, and the pipeline continuing anyway (failing later because the maven part hadn't actually completed).

I haven't been able to confirm, but my strong suspicion is mvn has been killed by the linux OOM killer.

Digging in SO, when processes are killed in this way, the 'return code' alone isn't valid. (http://stackoverflow.com/questions/7180970/return-code-when-oom-killer-kills-a-process). I'm not sure the best way to figure this out, as of course bash is calling a script (mvn) which is in turn calling java (the actual maven process that'd be the one being killed).

---
Originally reported by magnayn, imported from: Shell process killed (OOM), but pipeline continues anyway

• assignee: jglick
  
• status: Open
  
• priority: Major
  
• component(s): durable-task-plugin
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 3
  
• imported: 2025-12-09
  

Raw content of original issue

I have a jenkins pipeline, that invokes mvn with a 'sh mvn ....' invocation.


Occasionally, the output shows the maven execution suddenly stop, and the pipeline continuing anyway (failing later because the maven part hadn't actually completed).


I haven't been able to confirm, but my strong suspicion is mvn has been killed by the linux OOM killer. 


Digging in SO, when processes are killed in this way, the 'return code' alone isn't valid. (http://stackoverflow.com/questions/7180970/return-code-when-oom-killer-kills-a-process). I'm not sure the best way to figure this out, as of course bash is calling a script (mvn) which is in turn calling java (the actual maven process that'd be the one being killed).

• environment: linux