First, the continuous integration of the steps:
1, continuous compilation 2, continuous database integration 3, continuous testing 4, continuous review 5, continuous deployment 6, continuous feedback Two, continuous integration tools--hudson1, installation Hudson2, prepare Subversion warehouse formally established Hudson Continuous integration tasks, Need to prepare version control systems such as CVS, Subversion, Git, mercurial, etc. The book uses Subversion. A project named account is created, and all content under the project directory is submitted to the/account/trunk path of the SVN repository.3. Basic system setup of HudsonThe basic settings for the Hudson system include the JDK installation location and MAVEN installation information, and Hudson will use the configured JDK and MAVEN for continuous integration tasks. 4. Create a Hudson Task (1) New task Hudson a project built with a continuous integration of MAVEN, ANT, Shell and other build tools. As an example of a MAVEN project, you need to create a new Hudson task of type build a Maven2 project. (2) Task basic configuration such as project name, description, save cycle of build file. (3)source repository configuration for TasksConfigure the SVN address above and enter the user name password. (4) The construction of the task triggers the way the configuration build triggers trigger the build, including: Trigger the build of the project after other projects have been built; periodically build this project; Periodically poll the source repository svn and find out when there is an update to build this project ; (5) The configuration of the task is configured to build the project using the command that runs MAVEN, such as Hudson. (6) Monitoring task status (7) Hudson User Management (8) Message feedback informs the relevant team members of the integrated status information in a timely manner. (9) Hudson working directory Linux for/home/user/.hudson/
From for notes (Wiz)
"Maven Combat" note-The Continuous integration