I changed the default ant configuration in jenkins job to a custom installation and that worked. But this issue should not still appear if the default jenkins is used.

So JENKINS-8614 just worked around the issue in tests.
From what I see, the shortcut is to just disable FINE logging for the class https://github.com/kohsuke/winp/blob/master/src/main/java/org/jvnet/winp/WinProcess.java#L66
Working on a better solution

Disclaimer: the workaround above applies only to that particular stacktrace in the issue description, it does not help in the case of other failures, e.g.

org.jvnet.winp.WinpException: Failed to read environment variable table error=299 at .\envvar-cmdline.cpp:201 
at org.jvnet.winp.Native.getCmdLineAndEnvVars(Native Method) 
at org.jvnet.winp.WinProcess.parseCmdLineAndEnvVars(WinProcess.java:126) 
at org.jvnet.winp.WinProcess.getEnvironmentVariables(WinProcess.java:121) 
at hudson.util.ProcessTree$Windows$1.getEnvironmentVariables(ProcessTree.java:452) 
at hudson.util.ProcessTree$OSProcess.hasMatchingEnvVars(ProcessTree.java:276) 
at hudson.util.ProcessTree$Windows.killAll(ProcessTree.java:478) 
at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:965) 
at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:956) 
at hudson.remoting.UserRequest.perform(UserRequest.java:121) 
at hudson.remoting.UserRequest.perform(UserRequest.java:49) 
at hudson.remoting.Request$2.run(Request.java:325) 
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) 
at java.util.concurrent.FutureTask.run(Unknown Source) 
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) 
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) 
at hudson.remoting.Engine$1$1.run(Engine.java:69) 
at java.lang.Thread.run(Unknown Source)

I will check if there is a better solution I could apply

I am currently working on the fix. I wish I could just take the implementation from processhacker2 "https://github.com/processhacker2/processhacker2/blob/69d9dcd2c79d52ce987cc8f0150f639426eb67f9/phlib/native.c#L867-L990", but it cannot be done since the code there is GNU GPL. Will consider alternatives

Partial fix in WinP, which reduces the issue frequency: https://github.com/kohsuke/winp/pull/34

I had the exact error and call stack described in this JIRA issue. The solution for me was to disable Git Credential Manager as as described in the following: https://support.cloudbees.com/hc/en-us/articles/221046888-Build-Hang-or-Fail-with-Git-for-Windows

It took me hours to find that article, so I hope this helps someone. I know CloudBees is involved in the new development for Jenkins, so there should be consolidation or cross-linking of such issue reports and solutions. It was a surprising solution, since I last updated Git for Windows a long time ago and the Jenkins pipeline ran fine until today.

Hi Dustin. Are you sure you had exactly the same as in the ticket (winp, error 299)? I will try to reproduce, but I do not see a direct relation

WinP 1.25 improves diagnostics of the issues happening when accessing processes in the native part: https://github.com/kohsuke/winp/blob/master/CHANGELOG.md#125 . It will also prevent the reported issue when Jenkins does not actually need environment variables.

Created  JENKINS-44368 to update the core

Code changed in jenkins
User: Oleg Nenashev
Path:
core/pom.xml
http://jenkins-ci.org/commit/jenkins/6f9a833f9236b33406843cba57b765036ad4b334
Log:
JENKINS-44368 - Update WinP to 1.25 in order to improve diagnostics of issues like JENKINS-30782

Code changed in jenkins
User: Oleg Nenashev
Path:
core/pom.xml
http://jenkins-ci.org/commit/jenkins/bfd1f088e3ffa40260501fd2dbd9c196aad6be40
Log:
Merge pull request #2893 from oleg-nenashev/winp/1.25

JENKINS-44368 - Update WinP to 1.25 in order to improve diagnostics of issues like JENKINS-30782

Compare: https://github.com/jenkinsci/jenkins/compare/a27b73993d26...bfd1f088e3ff

Starting from 2.62 there is improved diagnostics in the library.

If you still see the issue, please try this version and report the results

I am closing this issue because WinP 1.25 offers some fixes and extra diagnostics. I you still experience the issue on newer versions, please reopen the issue