The execute windows batch command is a pretty reliable shell so it may still be that it is having trouble seeing that python is an available command.
This should be easy to test. Just go to the slave machine and open a command shell in the directory where your Jenkins workspace for that project is set to and try to run the python command. If it fails to come up there you need to set up new python environment variables. Things to double check: 1. Make sure python is working outside of Jenkins. 2. That your PATH contains the path to the python bin, exp C:\python\bin\; 3. You have restarted your computer since updating this variable 4. Double check the bin location to make sure your install is still valid. -- View this message in context: http://jenkins-ci.361315.n4.nabble.com/Jenkins-Plugin-Running-Scripts-on-Slave-Machines-tp4655674p4704148.html Sent from the Jenkins dev mailing list archive at Nabble.com. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
