Generally a duplicate, but not much to do here unless there is a known way to reproduce from scratch.

I have similar issue (Linux master and Windows slave), I can locally easily reproduce at will if this may help or some run test are needed.

Generally these cases mean that the wrapper cmd process has exited but failed to leave behind an exit status file. If you can reproduce at will, then try to track down why that exit status file is not being written. Probably a lack of handling for some corner case of Windows process management in the wrapper command, which you could reproduce outside Jenkins.

Note that there is an effort underway to create a Powershell launcher, which would presumably have its own set of bugs, but perhaps not any affecting you.

Where/How can I monitor this exit status file exactly?

Can I look somewhere onto the client or server file system? Or do I have to run Jenkins into a debug mode?

Can you point where this exit status is handled into the Jenkins code so I can have an idea of where to look?

Thanks

P.S.: I don't see Powershell as a savior of everything it will come with his set of execution policy and permission nightmare for those kind of thing. I personally would rather have a Python wrapper and do my own subprocess if needed there.

All relevant files will be on your build agent in a …/workspace/jobname@tmp subdirectory. Here is a good place to start in the code.

the same at my PC.

If the relative path is used in "Jenkins\Manage\Workspace Root Directory", then this issue comes.

If the path is absolute path then it is OK.

This is the content of jenkins-wrap.bat

pipe_build is the pipeline job name.

D:\jenkins\relFromYoon{color:#ff0000}ws\pipe_build{color:#ff0000}ws{color}pipe_build__tmp\durable-02c0f35d\jenkins-wrap.bat --> this file doesn't exist

@echo off
cmd /c ""ws\pipe_build\ws\pipe_buildtmp\durable-02c0f35d\jenkins-main.bat"" > "ws\pipe_build\ws\pipe_buildtmp\durable-02c0f35d\jenkins-log.txt" 2>&1
echo %ERRORLEVEL% > "ws\pipe_build\ws\pipe_buildtmp\durable-02c0f35d\jenkins-result.txt"

jenkins-wrap.bat should be placed on D:\jenkins\relFromYoon\ws\pipe_build\pipe_build__tmp\durable-02c0f35d\

I found if the job name is contains chinese ,this bug can ed reproduced,