Jenkins integrated robotframework

The concept of continuous integration

Continuous Integration (CI) is a practice that enables teams to receive feedback on an ongoing basis and make improvements, do not have to wait until after the development cycle to find and fix defects.

There are several aspects of its benefits:

● errors quickly: every little update is completed, it is integrated into the trunk code, you can quickly find errors, positioning errors is relatively easy.

● prevent substantial deviation from the trunk branch: If it is not often integrated, skeleton code and is continually updated, will lead to the future integration of difficulty increases, even difficult to integrate.

● reduce repetitive work: You can compile, deployment, testing and other actions have become automated through automated continuous integration, without too much manual intervention.

Deployment job lines, so that an application from the build, deploy, test, and release automate this process is the core component of the modern concept of DevOps. In different internal business, the specific implementation of the deployment pipeline is not the same, but the basic principle is the same.

General common line: submit code -> static code scanning -> unit testing -> compiler package -> Automatic Deployment -> Interface test automation -> UI test automation -> Publish the production environment -> User validation phase

Deployment:

1, trigger construct: the development environment for the deployment, a developer code or merge code to push master branch svn project, Jenkins to the corresponding server code is deployed.

2, the parameters of the building: pre-wired for a test environment deployment environment, develop code or push to the master branch svn merge code after the project, and will not deploy code, but jenkins need to log into the web interface, click on the build button, biography the corresponding parameters (such parameters need to build tag, you need to deploy a branch) and before deployment.

3, time to build: for automatic packaging, the timing is based on parametric building built on to add, developers can log incoming jenkins manually tag is packaged, if not manually packed, so get the latest from the SVN jenkins pull it every morning the code package.

The basic configuration of continuous integration

This whole idea of the deployment environment technical solutions: SVN + RF + Jenkins + nginx + cenos7 + Allure

New node

System Administration -> Node Manager -> New node
VM cetnos system deployment Jenkins platform, master master node management sub-nodes, because the project is a windows environment is performed based on the use case, you need to add a child node windows environment, of course, also be added based on the linux environment sub-node, depending on the operation of the project environment set.
Add a child node can be a physical machine or a virtual machine.
The action tag corresponding to the tag of each child node which hosts which host Station Idle calls automatically performed Construction

New child nodes, the platform will be prompted to download the slave-agent.jnlp child node machine, not through the command line to start the child nodes of child nodes. As shown below:

Here by opening the Control Panel JAVA script starts running, the child node slave-windows become online. As shown below:

New job

Here the freedom to choose the style software project, and then set the job task name.

General Configuration

Here choose to discard the old construction, constructed to maintain the number of days to build three days, the maximum number of three, arranged to limit operation of the node label robot, other parameters depending on the actual items and more environment.

Source Management

Set SVN repository path and account password
Other default, other parameters can also be configured according to the actual situation

Trigger builder

● Construction of a timing point of time represented by the set automatically trigger a build

● polling SCM submit code indicating the detection to SVN and automatically trigger a build, this setting every 5 minutes SVN detection state as long as the state change trigger after 5 minutes Construction

● SVN detection state, need to modify the hook script in SVN repository master server node Jenkins

● Timing task trigger time expression

Using a configuration known UNIX CRON task scheduling tool used. With five fields represent the five different time units (separated by spaces):

Time-moon and day of the week

For example:

02 * * * indicates 2:00 every day

* / 10 * * * * every 10 minutes

45 10 * * 1-5 Monday through Friday 10:45 min execution

Construct

● presentation environment is not currently involved in the build environment, depending on the actual project and environment.

● The project is based on windows to perform automation use cases, here select windows batch command, which is automatically issued when constructing command automation use cases

● If the project is running on linux environment, you need to select the option to execute the shell and set the parameters