Bug 486217 - Hudson fails to send the SIGTERM signal when a build is killed
Summary: Hudson fails to send the SIGTERM signal when a build is killed
Status: NEW
Alias: None
Product: Hudson
Classification: Technology
Component: Core (show other bugs)
Version: 3.3.2   Edit
Hardware: All All
: P3 critical (vote)
Target Milestone: ---   Edit
Assignee: Winston Prakash CLA
QA Contact: Geoff Waymark CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-20 22:06 EST by Hongyuan Yi CLA
Modified: 2016-01-20 22:06 EST (History)
4 users (show)

See Also:

Attachments
Issue reproduction info (72.97 KB, message/rfc822)
2016-01-20 22:06 EST, Hongyuan Yi CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Hongyuan Yi CLA 2016-01-20 22:06:23 EST 
Created attachment 259289 [details]
Issue reproduction info

When a build is killed, Hudson 2.2.0 sends a SIGTERM. We trap it and perform some proper cleanup and post build steps, especially to make sure multi-platform builds are aborted properly. This is a critical feature to us. This issue causes multiple builds to run at the same issues, and it is problematic on Windows.
 
However, it seems Hudson 3.3.2 doesn’t do that anymore. We are not able trap SIGTERM. We re-set up a Hudson 2.2.0 server and it still works as we understand.