This is an example jenkins job with extendable default settings. If you want to create a new job us this job as a template. <ol> <li>If you don't already have a user account on https://ci.inria.fr <ul> <li> request one on the <a href="https://ci.inria.fr/users/new">Inria Continuous Integration portal</a></li> <li> check your inbox! You need to click on the activation link to get a fully working account</li> <li> go to <a href="https://ci.inria.fr/project">the project list</a> and look for pharo-contribution. Request to join it.</li> <li> wait that an admin of pharo-contribution accepts your request. You will be notified by email.</li> <li> once the join request accepted, you are able to connect on <a href="https://ci.inria.fr/pharo-contribution">https://ci.inria.fr/pharo-contribution</a> with the account created on https://ci.inria.fr.</li> </ul> </li> <li>Click on <a href="/pharo-contribution/view/all/newJob"><img height="24" style="margin: 2px;" alt="" width="24" src="/pharo-contribution/static/d176eb47/images/24x24/new-package.png"> New Job</a> </li> <li> Set a title (usually the package name of your Pharo project) and choose Copy existing Job and select <code>JobTemplate</code> </li> <li> Write a meaningful project description (required) with a contact information </li> <li> Adapt the properties of the Build: <ul> <li> [URLTrigger] - Poll with a URL: set the proper URL of the source MC repository </li> <li> Matrix Configuration - PHARO: On which Pharo version should your project be tested? (<code>20</code>) </li> <li> Matrix Configuration - VERSION: Which version of your Metacello Configuration should be tested? (<code>development</code>, <code>stable</code>, <code>last</code>, <code>bleedingEdge</code> or a version number) </li> <li> Matrix Configuration - VM: Which VM should be used for testing your project? (<code>vm</code> or <code>vmS</code>) </li> </ul> </li> <li> Finally adapt the build script if necessary. Usually the <code>$REPO</code> variable has to be changed to the one specified for the URLTrigger settings. Furthermore the default settings assume that the Jenkins job has the same name as your Pharo project and thus the configuration. The Jenkins job named <a href="/pharo-contribution/job/Soup">Soup</a> uses a Metacello configuration named <code>ConfigurationOfSoup</code> and runs all tests in the packages matching <code>Soup.*</code>. </li> <li> Try and run your job. Not that test results are only visible after the second run. </li> </ol> 30 -1 -1 -1 false https://github.com/cormas/cormas/ false true false false false @daily @hourly http://smalltalkhub.com/mc/SergeStinckwich/CORMAS/main false false 200 300 false false true false false PHARO 40 VERSION stable development VM vm # jenkins puts all the params after a / in the job name as well :( export JOB_NAME=`dirname $JOB_NAME` wget --quiet -O - get.pharo.org/$PHARO+$VM | bash ./pharo Pharo.image save $JOB_NAME --delete-old ./pharo $JOB_NAME.image --version > version.txt REPO=http://smalltalkhub.com/mc/PharoExtras/$JOB_NAME/main ./pharo $JOB_NAME.image config $REPO ConfigurationOf$JOB_NAME --install=$VERSION ./pharo $JOB_NAME.image test --junit-xml-output "$JOB_NAME.*" zip -r $JOB_NAME.zip $JOB_NAME.image $JOB_NAME.changes # clean up the workspace to not occupy too much stale space on the slaves rm -rf *.image *.changes **/*.zip, **/version.txt, **/*Test*.fuel true false **-Test.xml false false

true false true true true true true true false false 15 false false xterm 0 false false 10 false false