Re: Not able to run MATLAB execution using shell script.

2014-06-27 Thread Rachit Kumar
Hello Guys, Thanks a lot for your input, the issue has been resolved. The problem is in the Project configuration. It was configured for Windows and I was running it on Linux. Sorry for your time, thanks a lot! On 26 June 2014 14:47, Vivekanand S V wrote: > If you can execute matlab using your

Re: Not able to run MATLAB execution using shell script.

2014-06-26 Thread Vivekanand S V
If you can execute matlab using your user account from terminal and you are using the same accoutn while running the job, add this line in your "execute shell" step export PATH=$PATH:/usr/local/MATLAB/R2014a/bin/ That should point to the correct executable. You can try the above step even if you

Re: Not able to run MATLAB execution using shell script.

2014-06-26 Thread Rachit Kumar
Hello Richard, Modification: #!/bin/bash /usr/local/MATLAB/R2014a/bin/matlab -nosplash -nodisplay -r "InitFileName='model_init',VariableList={'motorspeed' 'motorpositions' 'voltage'},SimStart=0,SimEnd=20,ModelName='jenkins_test_model';jenkins_matlab" It gives the following error: [MATLAB_Jen

Re: Not able to run MATLAB execution using shell script.

2014-06-26 Thread Richard Bywater
Another option is just to change the shell script and put the path in there (e.g. change matlab to /opt/matlab/bin/matlab or whether the matlab executable is) Richard. On Thu, Jun 26, 2014 at 9:59 PM, Rachit Kumar wrote: > Frankly I am new to Jenkins and new to Linux environment as well! > How

Re: Not able to run MATLAB execution using shell script.

2014-06-26 Thread Rachit Kumar
Frankly I am new to Jenkins and new to Linux environment as well! How can I check what is th euserid jenkins is using and how do I set the PATH for that userid. Also I do not have root access, so will it be possible for me to change the PATH of Jenkins userid and and run the MATLAB simulation. T

RE: Not able to run MATLAB execution using shell script.

2014-06-26 Thread Matthew.Webber
Doesn’t matlab: command not found tell you what the problem is? If it works from the terminal but not under Jenkins, then the PATH is presumably different in the two cases. Did you try in from the terminal using the same userid that Jenkins runs under? From: Rachit Kumar [mailto:tihcar.ra...@gm