How to use Jenkins for continuous integration testing

In this article, we built the continuous integration test environment of Jenkins, and then we started our creation task and run the build.
(i) Create a task
1. Create a task
Click on the "Create a new task" link on the homepage below:

2. Choose the Jenkins task type
Jenkins offers four types of tasks:
1) Build a free-style software project
This is the main function of Jenkins. Jenkins will build your project in conjunction with any SCM and any build system, and can even build
Systems other than the software.
2) Build a MAVEN project
Build a MAVEN project. Jenkins uses your POM file, which can greatly reduce the build configuration.
3) Build a multi-configuration project
For multi-configuration projects, such as multi-environment testing, platform-specific builds, and more.
4) Monitor an external task
3. This type of task allows you to record the tasks performed on the outside Jenkins, and the task even runs on the remote machine. This allows Jenkins to act as a control panel for all your automated systems.
Select the first item "Build a free-style software project" and click "OK". The detailed configuration page for entering the project is as follows:

4.
5. Add Build Steps

We chose Execute Windows Batch command to create a batch under Windows.
Let's say that I have a htmlresportemail_4.py script in the C:\Python34 directory, and we're going to run this script at the command prompt to do this:

Then in the Excute Windows Batch Command window, there is

If no additional steps are required, then here the task creation is complete and we can click Save.

(ii) Operational construction

The list on the left is an action about the project.
If you need to modify the configuration information just now, you can click the "Configure" link to re-modify it.
Click the "Build Now" option and build history will show you the project's build status.

After the run is finished,

Click Console Output

View to Jenkins log:

Check the mailbox again, and test report is automatically sent to the mailbox,

In this way, continuous integration testing with Jenkins is complete.
Once felt out of reach, after all at al. Automated testing is jenkins+linux and a variety of tool automation test environments, and now in the Windows environment, today is finished.

Looking at the once familiar Jenkins environment in the Windows system Configuration run completed, mixed feelings, for the first owner, where a lot of growth, contact with a lot of very nice colleagues and manager,leader, their thoughts, their life and face the attitude of living , will affect my life, this is my life's wealth. Happiness is accompanied by the growth of the North drift 3 years.
One of the meanings of effort is that I can say no to some.

How to use Jenkins for continuous integration testing