-
Bug
-
Resolution: Not A Defect
-
Major
-
Windows Server 2008
I have a .bat file that will start some servers and running that bat with a simple double click works just fine.
Running the same bat file from Jenkins will start the execution but will produce some errors due to console input problems on that .exe file called from batch.
It should be no difference between those 2 ways of running batch files...
13:38:54 ${SOME_PATH}>shared\api\ServerManagerClient.exe /wait:5 /serverManager:localhost:7764 /command:addServer /gn:OrderBook /sn:ManualAdapter /in:TS_ManualAdapter /pcu:file:/${SOME_PATH_2} /wd:${SOME_PATH_3}
13:38:54 Error executing command 'addServer'
13:38:54 Cannot see if a key has been pressed when either application does not have a console or when console input has been redirected from a file. Try Console.In.Peek.
This is not a Jenkins bug. Your program seems to require an interactive session or needs to be called in an interactive cmd, which is not the case in Jenkins.
To get assistance (e.g. workarounds, how to configure Jenkins so this works, if possible), please ask on the jenkinsci-users mailing list, or in #jenkins on Freenode.