build with Jenkins configuration AutomationCategory: Integrated system configuration 2013-03-06 14:11 63845 People read Comments (Ten) favorite reports Jenkins Auto Buildcontinuous integration is a simple repetition of labor, people to operate time and effort, the use of automated building tools to complete the best. In order to fulfill this requirement, I chose Jenkins. Download the latest installed version of Jenkins from Http://mirrors.jenkins-ci.org/windows/latest under Windows. (If unable to install, download the war package from Http://mirrors.jenkins-ci.org/war/latest/jenkins.war, manual configuration, configuration instructions see https://wiki.jenkins-ci.org/ Display/jenkins/use+jenkins). 1. Install here directly using the installation package, the installation process is very simple, here is explained again. After installation, a Windows service is created automatically: Jenkins, the default port is 8080, if necessary, open the Jenkins.xml file under the installation directory, modify the <arguments>-xrs-xmx256m- Dhudson.lifecycle=hudson.lifecycle.windowsservicelifecycle-jar "%base%\jenkins.war"--httpport=8081</arguments> after saving, start Jenkins service. Open http://192.168.0.10:8081/and see an interface similar to the following (I have created a task here):
Indicates that Jenkins has been successfully installed. 2. Create Task 2.1 "New Job", the interface is as follows:
Enter the task name, any name, but preferably a meaningful name, enter the same name and project name as Hummer 2.2 to select the project type, because my project is a MAVEN project, select "Build a MAVEN2/3 project " Click OK" To enter the next screen. The 2.3 interface is as follows:
source control according to their own needs to choose, my source code is using SVN management, here Select "Subversion Modules", in "Repository URL" input your SVN warehouse address , the first time input also need to enter the SVN repository username and password. the interface is larger, scrolling down, the interface of the middle section is as follows:To build the trigger, I select theBuild whenever a SNAPSHOT dependency is built ", which means that depending on the build of the snapshot, the project should be built when SVN has been modified. 2.4 Build settings do not have to be modified, use Pom.xml, and the target option is not modified. 2.5 Set the post-build steps, (post Steps, optional settings), I'll ask you to copy the war file to the specified directory after the build succeeds, then deactivate Tomcat, delete the Project Web directory, and start Tomcat. 2.6 Setting up email notificationsChecke-Mail Notification ", in the recipients to enter the mail to receive the mailbox. Click "Save" to complete setting 3. Start building the project by clicking "Build Now" on the left menu of the work area.
If the build succeeds, the state of the project is blue and red if it fails.
When the build is complete, the left menu will show "console output" and click to view the console verbose output. Build errors can also be modified according to the appropriate error message.
Copyright NOTICE: This article for Bo Master original article, without Bo Master permission not reproduced.
Build with Jenkins Configuration automation
