Jenkins continuous integration server: Difference between revisions
Jump to navigation
Jump to search
Content deleted Content added
imported>Madmetzger |
imported>Madmetzger |
||
| Line 43: | Line 43: | ||
The other options allow it to start a build via URL or let a build start, if another build was finished. |
The other options allow it to start a build via URL or let a build start, if another build was finished. |
||
=== |
===Build Steps=== |
||
To build Stendhal with hudson, we just execute three targets from the standard build.xml included in stendhal source code. We let hudson first call ''clean run_tests_with_cobertura''. This first cleans the workspace and starts a complete build including coverage measurement. Afterwards we start ''java_doc'' which generates a fresh api documentation from stendhal. |
|||
{{TODO|JDK}} |
|||
=== |
===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. |
|||
{{TODO|Build Job}} |
|||
* java doc |
|||
:* check this option to publish the generated java docs |
|||
:* provide ''api'' as directory for the docs |
|||
* junit test results |
|||
:* check this option to publish the results |
|||
:* provide ''build/build_test_report/testresults.xml'' as location for the junit report in xml format |
|||
* cobertura |
|||
:* this option allows us to publish the results of the test coverage |
|||
:* provide ''build/cobertura_report/*.xml'' as report file |
|||
* To do report |
|||
* Warnings |
|||
==Known Problems== |
==Known Problems== |
||