编辑“︁Jenkins continuous integration server”︁（章节）

==Setup a build job for Stendhal==

The next steps show how to configure a basic build job for Stendhal.

===Source Code Management===

==== Build from Git ====

To build from Git, you need to have the [https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin Git plugin] installed. Just select Git and configure the following parameters:
* Repository URL
:* <code>file:///your/path/to/stendhal</code>
* Branches to build
:* leave this empty if you want to build HEAD.
:* or choose a branch name to build

==== Build from the working copy ====

To build from the working copy:
* have the [https://wiki.jenkins-ci.org/display/JENKINS/File+System+SCM File System SCM] plugin installed
* select "File System" from "Source Code Management"
* Path: <code>/your/path/to/stendhal</code>

===Build Trigger===

Here you configure when a build is started. A possible way is triggering from Git at a certain time. This doesn't mean that Git tells Jenkins to start a build, but it tells Jenkins to check regularly on 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.

For both of this options you have to provide a cron like notation, when to check/build. For example, you could check every day at 5 am and build then.

===Build Steps===
To build Stendhal with Jenkins, we just execute three targets from the standard <code>build.xml</code> included in Stendhal source code. We let Jenkins first call <code>clean test</code>. This first cleans the workspace and starts a complete build including coverage measurement. Afterwards we start <code>docs</code> which generates a fresh API documentation from Stendhal.

===Post Build Processing===
After a build was successful certain steps follow to produce those nice looking reports and graphics. For Stendhal we use several reports to publish.
* Publish Javadoc
:* check this option to publish the generated Java docs
:* provide ''api'' as directory for the docs
* Publish JUnit test result report
:* check this option to publish the results
:* provide <code>**/build/build_test_report/testresults.xml</code> as location for the JUnit report in XML format
* Record JaCoCo coverage report
:* this option allows us to publish the results of the test coverage
:* provide <code>**/build/build_server</code> as ''Path to class directories''
:* provide <code>**/src</code> as ''Path to source directories''
* To do report
* Warnings