Revision as of 19:27, 26 November 2013 view source imported>Balaur →Source Code Management System: file system ← Older edit		Revision as of 18:52, 5 March 2016 view source imported>Balaur s/cvs/git. s/cobertura/jacoco. Emphasis on local server. Newer edit →
Line 3: Jenkins is an extensible continuous integration server. ~~You~~Some ~~can~~developers ~~have~~use ~~a look at [http://stendhalgame.org/jenkins/ our~~local Jenkins ~~server]~~instances ~~with~~for ~~several build jobs for~~building Stendhal~~, Marauroa~~ and ~~Marboard~~Marauroa. <div style="border: 1px solid red; padding: 1em">The rest of this article deals with the installation and configuration of Jenkins. If you are just interested in the results, please follow this link to [http://stendhalgame.org/jenkins/ our Jenkins server] above. ~~</div>~~ In production we don't use Jenkins, but [https://travis-ci.org/arianne/ Travis]. ==Installation== To install and run Jenkins you just need to download the <code>jenkins.war</code> from the Jenkins web site and have ~~java~~Java ready. To start the server you need a small start script that issues the following command: java -jar jenkins.war Once ~~the jenkins~~Jenkins is started, you can reach the user interface via your favourite browser if you open the following URL (assuming you have Jenkins on the same machine as your browser): http://localhost:8080 If you see the Jenkins interface loading, you have successfully installed Jenkins. ==Configuration for Stendhal== To let Jenkins build ~~stendhal~~Stendhal you have to match the following ~~prerequesites~~prerequisites: * ANT installed on the same system * JDK 7 installed * JDK1.5 installed (already matched if you were successfully running Jenkins, as it needs java to run) * ~~CVS-Client~~Git installed ~~For~~Here ~~our~~is ~~Jenkins~~a welist ~~installed~~of ~~several~~Jenkins plugins that you may want to install via the Jenkins configuration. You can see what each plugin does, if you have a look at ~~our Jenkins or look~~ onto the wiki at the Jenkins homepage~~. This list is not complete, as we still experiment with some of the plugins~~. * [~~http~~https://wiki.jenkins-ci.org/display/JENKINS/~~Cobertura~~Git+Plugin ~~Jenkins~~Git ~~Cobertura plugin~~Plugin]▼ ** if you want to build from a Git repository * [https://wiki.jenkins-ci.org/display/JENKINS/File+System+SCM File System SCM Plugin] ** if you want to build directly from the working copy (without committing) * [https://wiki.jenkins-ci.org/display/JENKINS/Xvnc+Plugin Xvnc Plugin] ** You may want to install this if some tests that depend on Swing fail with an error like ''«No X11 DISPLAY variable was set, but this program performed an operation which requires it»'' (see http://stackoverflow.com/q/12533339/479288). Other plugins to try: * [http://wiki.jenkins-ci.org/display/JENKINS/Audit+Trail+Plugin Audit Trail] * [http://wiki.jenkins-ci.org/display/JENKINS/Checkstyle+Plugin Checkstyle Plugin] ▲* [http://wiki.jenkins-ci.org/display/JENKINS/Cobertura+Plugin Jenkins Cobertura plugin] <!--* [http://jenkins.gotdns.com/wiki/display/JENKINS/Crap4J+Plugin Jenkins Crap4J plugin]--> <!--* [http://wiki.jenkins-ci.org/display/JENKINS/Emma+Plugin Jenkins Emma plugin]--> Line 43 ⟶ 47: ==Setup a build job for Stendhal== The next steps show, how to configure a basic build job for ~~stendhal~~Stendhal. ===Source Code Management ~~System~~=== ==== Build from ~~CVS~~Git ==== To build from ~~CVS~~Git, ~~just~~you need to have the [https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin Git plugin] installed. Just select ~~CVS~~Git and configure the following parameters: * Repository URL * CVS-Root :* <code>file:///your/path/to/stendhal</code> ~~:* :pserver:anonymous@arianne.cvs.sourceforge.net:/cvsroot/arianne~~ * Branches to build * Module :* leave this empty if you want to build HEAD. ▼ ~~:* stendhal~~ * Branch ▲:* leave this empty if you want to build HEAD. :* or choose a branch name to build Line 66 ⟶ 68: ===Build Trigger=== Here you configure, when a build is started. Our current way of triggering builds is triggered from CVS at a certain time. This means not, the CVS tells Jenkins to start a build, but it tells Jenkins to check regularly the CVS for changes and builds, when there were commits since last build.▼ ▲Here you configure, when a build is started. ~~Our~~A ~~current~~possible way ofis triggering ~~builds is triggered~~ from ~~CVS~~Git at a certain time. This ~~means~~doesn't ~~not,~~mean ~~the~~that ~~CVS~~Git tells Jenkins to start a build, but it tells Jenkins to check regularly ~~the~~on ~~CVS~~Git for changes and builds, when there were commits since the last build. You also can start build at certain times not regarding changes since last build.▼ ▲You also can start build at certain times not regarding changes since last build. ~~For both of this options you have to provide a cron like notation, when to check/build. At the moment, we check every day at 5 am and build then.~~ ~~The~~For ~~other~~both of this options ~~allow~~you ithave to ~~start~~provide a ~~build~~cron ~~via~~like ~~URL~~notation, orwhen ~~let a~~to check/build. ~~start~~For example, ifyou ~~another~~could ~~build~~check ~~was~~every day at 5 am and build ~~finished~~then. ===Build Steps=== To build Stendhal with Jenkins, we just execute three targets from the standard <code>build.xml</code> included in ~~stendhal~~Stendhal source code. We let Jenkins first call ''<code>clean ~~run_tests_with_cobertura''~~test</code>. This first cleans the workspace and starts a complete build including coverage measurement. Afterwards we start ~~''java_doc''~~<code>docs</code> which generates a fresh ~~api~~API documentation from ~~stendhal~~Stendhal. ===Post Build Processing=== After a build was successful certain steps follow to produce those nice looking reports and graphics. For ~~stendhal~~Stendhal we use several reports to publish. * Publish Javadoc * java doc :* check this option to publish the generated ~~java~~Java docs :* provide ''api'' as directory for the docs * ~~junit~~Publish JUnit test ~~results~~result report :* check this option to publish the results :* provide ''<code>*/build/build_test_report/testresults.xml''</code> as location for the ~~junit~~JUnit report in ~~xml~~XML format Record JaCoCo coverage report * cobertura :* this option allows us to publish the results of the test coverage :* provide ''<code>*/build/~~cobertura_report~~build_server</.xmlcode> as ''Path asto ~~report~~class ~~file~~directories'' :* provide <code>*/src</code> as ''Path to source directories'' To do report * Warnings ~~==Known Problems==~~

Jenkins continuous integration server: Difference between revisions