Continuous integration Java manual

Continuous integration Java manual

First, concept

Martin Fowler's article: Continent Integration Chinese Translation: Continuous Integration

Second, tools

Traditional tools: JBuilder, VisualsourceSafe, Rational Clearcase

Auto Compilation Tool: Ant

Return test Tool: JUnit

Code Check Tool: Checkstyle

Continuous integration tool: CruiseControl

Third, step

CruiseControl monitoring changes in the remote version control system When the CruiseControl call compilation tool compiles (Ant, etc.) After the compilation is successful, call JUnit to return to the test. After successful, call CheckStyle to check the package, deploy, update the version control system, compile the results after completion , Test results, code check results are sent to developers, executive managers, and publish to websites, and even alarm

All this is automatically carried out according to the prepared script

Fourth, the implementation example

At present, we use ClearCase, the master software is CruiseControl, its script file is cccc.xml

Configure a remote version control system

Configure compilation tool

Configure test case (in Ant configuration file)

Configuration report

Where CruiseControl has no support for code inspection tools, it is recommended to use Ant to call Checkstyle, and examples are as follows (no truly run):