title: Jenkins cannot run exe batch commands?
body: <p>Ultimately trying to run some <code>NUnit</code> web tests, but I found that Jenkin's would stop before running the batch command <code>path\to\nunit.exe</code>.  So I just tried running a new job that consists of a single build step:  Execute Windows batch command <code>C:\Windows\system32\calc.exe</code>.  Here is my console output:</p>
  
  <blockquote>
    <p>Started by user anonymous</p>
    
    <p>Building in workspace C:\Program Files (x86)\Jenkins\jobs\[my job]\workspace
    [workspace] $ cmd /c call C:\Windows\TEMP\hudson8921839713501090632.bat</p>
    
    <p>C:\Program Files (x86)\Jenkins\jobs\[my job]\workspace>C:\Windows\system32\calc.exe</p>
  </blockquote>
  
  <p>and there it hangs until I cut if off.  Needless to say, this command runs fine in command prompt.  Also, commands that do not open new processes run fine (e.g. dir) in <code>Jenkins</code>.  I don't know what the difference is between running batch commands in cmd.exe and running them through Jenkins.  I cannot find any remotely relevant information with a google search of <code>jenkins cannot open exe</code>.  Any advice is appreciated.</p>
  
  <p>Edit:</p>
  
  <p>While practicing Shiva's suggestion, I tried observing the running processes while I ran my Jenkins job.  If I do not precede the command with <code>start</code>, then <code>calc.exe</code> does run but the interface does not display.  Once I kill the jenkins job, calculator is killed as well.  If I do include <code>start</code>, then everything is the same except the jenkins job finishes on its own and the calculator continues to run after the job is over.  Here is the new log:</p>
  
  <blockquote>
    <p>Started by user anonymous
    Building in workspace C:\Program Files (x86)\Jenkins\jobs\First Job\workspace
    [workspace] $ cmd /c call C:\Windows\TEMP\hudson8285328547956378876.bat</p>
    
    <p>C:\Program Files (x86)\Jenkins\jobs\First Job\workspace><strong>start</strong> C:\Windows\system32\calc.exe </p>
    
    <p>C:\Program Files (x86)\Jenkins\jobs\First Job\workspace>exit 0 
    Process leaked file descriptors. See <a href="http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build" rel="nofollow noreferrer">http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build</a> for more information
    Finished: SUCCESS</p>
  </blockquote>
  
  <p>Although this is different behavior, I'm not sure that it offers further enlightenment.  Why can I not interact with the running processes?</p>
  
  <p>Possibly related:
  <a href="https://stackoverflow.com/questions/15947846/jenkins-wont-execute-correctly-a-command-from-a-bat?rq=1">Jenkins won&#39;t execute correctly a command from a .bat</a></p>