-
Bug
-
Resolution: Fixed
-
Major
-
Windows
-
-
1.38
Durable task is launched in the process tree of slave.jar process.
When slave agent exits, it doesn't kill durable tasks (ProcessTree utility excludes the detached build). But when the slave is managed as a Windows service, the service wrapper kills all processes of the process tree and consequently stops durable tasks.
Durable task should be launched in a dedicated process group isolated from slave.jar process tree.
- duplicates
-
JENKINS-51145 PowerShell pipeline step does not seem to be durable
-
- Closed
-
- is related to
-
JENKINS-25503 Use setsid instead of nohup
-
- Resolved
-
-
JENKINS-51145 PowerShell pipeline step does not seem to be durable
-
- Closed
-
- relates to
-
JENKINS-47657 Agent running as Windows service kills all running jobs on reconnect
-
- Resolved
-
- links to
[JENKINS-27617] Isolate durable task in a dedicated Windows process group
Description |
Original:
Durable task is launched in the process tree of slave.jar process. When slave agent exits, it doesn't kill durable tasks (```ProcessTree``` utility excludes the detached build). But when the slave is managed as a Windows service, the service wrapper kills all processes of the process tree and consequently stops durable tasks. Durable task should be launched in a dedicated process group isolated from slave.jar process tree. |
New:
Durable task is launched in the process tree of slave.jar process. When slave agent exits, it doesn't kill durable tasks ({{ProcessTree}} utility excludes the detached build). But when the slave is managed as a Windows service, the service wrapper kills all processes of the process tree and consequently stops durable tasks. Durable task should be launched in a dedicated process group isolated from slave.jar process tree. |
Link |
New:
This issue is related to |
Summary | Original: Isolate long running task in a dedicated process group | New: Isolate durable task in a dedicated process group |
Assignee | Original: Jesse Glick [ jglick ] |
Epic Link | New: JENKINS-35399 [ 171192 ] |
wmic process call create looks promising, if it can be made to pass Create_New_Process_Group.