-
Bug
-
Resolution: Fixed
-
Major
-
None
-
any
-
-
2.141
Using the freestyle projects to execute bash shell scripts work fine. But cancelling a jenkins job seems to use SIGKILL. In this way the script cannot perform cleanup operations and free resources.
SIGKILL cannot be handled by shell
SIGINT/SIGTERM are not used by jenkins
Preferred: SIGINT -> wait 5 seconds -> SIGKILL
- is related to
-
JENKINS-3105 Configuration UI to disable process tree killer selectively
-
- Resolved
-
-
JENKINS-55106 Build stuck on final "exit 0"
-
- Open
-
- relates to
-
JENKINS-59152 Jenkins fails to properly abort "bat" step
-
- Resolved
-
- links to
[JENKINS-17116] graceful job termination
Priority | Original: Minor [ 4 ] | New: Major [ 3 ] |
Link |
New:
This issue is related to |
Assignee | New: Kohsuke Kawaguchi [ kohsuke ] |
Workflow | Original: JNJira [ 147947 ] | New: JNJira + In-Review [ 177041 ] |
Assignee | Original: Kohsuke Kawaguchi [ kohsuke ] |
Assignee | New: Robin Jarry [ robinjarry ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Status | Original: In Progress [ 3 ] | New: In Review [ 10005 ] |
Remote Link | New: This issue links to "https://github.com/jenkinsci/jenkins/pull/3414 (Web Link)" [ 21430 ] |
Comment |
[ Final Edit - our issue was identified not related to the TERM kill but a rogue jenkins triggering a duplicate job ] |