-
Bug
-
Resolution: Unresolved
-
Major
Follow-up to JENKINS-22249 for WindowsBatchScript.
http://serverfault.com/questions/126502/how-to-get-own-process-pid-from-the-command-prompt-in-windows/126643#126643 is the only thing I can find for Windows. Ugly!
- is related to
-
JENKINS-22249 Record process ID of spawned process
-
- Resolved
-
- relates to
-
JENKINS-25503 Use setsid instead of nohup
-
- Resolved
-
-
JENKINS-42166 ProcessLiveness.workingLaunchers heuristic is flaky
-
- Resolved
-
- links to
With some modifications, perhaps using the process of capturing the PID from the attached bat script could help us track things better.
AFAIK, the wmic command has been available for quite some time, should go as far back as windows xp and server 2003, so I doubt we'd cause noticeable breakage by calling out to this tool.