Additional Info - nthakur34/JenkinsGithub GitHub Wiki

However, if we were to organize testing scripts so for example we have x scripts that run 10*x tests, it may be easier to type "H 0 * * *" or "H H * * *", which would run the tests evenly from 12:00 to 12:59am or 12:00am to 11:59am to lighten the load on the system. Of course this isn't required or even necessary for the CERR project, but may become important in the case of massive growth.
Many errors may occur during the build step. Matlab could have licensing issues through Jenkins. and a -c flag would need to be added and directed to the correct license. It may also simply not work, so matlab in the command prompt might need to be replace with the entire path C:\blabla\matlab. Of course, there could be many different issues that are beyond the scope of this tutorial. reading the console log in Jenkins can give you an idea of what's wrong however. For example, if the build always fails because Matlab won't start, it may be better to install a Tomcat Apache server and set it up to run Jenkins. Here are some excellent instructions on Mathworks.