I have a single batch file which calls a number of executables which builds 
various assets for our application.  When I run the batch file manually it 
works perfectly (the command prompt opens, the assets are built - takes 
about 10 minutes - and then it closes).

If I run this batch file via a build step, it successfully calls the batch 
file, but the individual steps inside the batch file fail (it just skips 
over each one).  I'm assuming this is down to some permission issue between 
the user used when I run the file manually and the user used when Jenkins 
runs it.

If I move the content of the batch file into the build step itself I get 
the same results.

In the System Information screen my user name is actually my computer name 
(with a $ on the end) rather than an explicit user as defined in my system 
admin.

What user is used to run build steps and how can I change that user?  Has 
anyone else experienced this problem before and has a solution?

Thanks
Lee

Reply via email to