Build a continuous integration environment based on Jenkins + GitHub

Building continuous integration first of all to understand what is continuous integration, with a clear goal to build a continuous integration environment in order to let us go a lot less detours. Continuous integration (continuous integration), or CI, is a software development practice that allows teams to receive feedback and improve on the basis of continuous integration without having to wait until later in the development to find and fix defects. Of course, it is clear that the building of continuous integration environment is not once and for all, as software project complexity increases, the continuous integration of the environment should also be maintained to ensure the reliability of the integrated environment.

Important elements of continuous integration: 1. A unified code base.

    2.CI Server

    3. Scripts for automated testing and construction

    4.Slaves

Continuous integration process: CI server controls the entire process of continuous integration, polls the code base for updates, builds projects based on predefined scripts, and the server assigns tasks to the slave side. This is the whole process of continuous integration, we need to develop a perfect continuous integration plan according to our project needs, then choose CI Server and version management software according to the plan, our project chooses the continuous integration environment of Jenkins+github, this is also I want to tell the main and everybody.

Why Choose Jenkins?

Jenins is now a very popular continuous integration CI server, which and its predecessor Hudson also has a great relationship, Jenkins easy to install, do not need database support, directly through the Web interface configuration, and integrated rss/email notification mechanism, support distributed construction, With a rich plug-in, these are the benefits of Jenkins compared to other continuous integration servers.

The choice of version control software depends on the project needs, perhaps SVN or git, in general Jenkins has to provide plug-in support, the following explains the Jenins+github continuous integration of the details of the environment.

The main process for this continuous integration environment is that Jenins will run in the background, polling the version-controlled repository, and when the repository changes are found, the project will be built with a predefined build script, and Jenkins will assign the task to the slave side based on the project requirements. The general project building process is divided into two phases: Automated compilation and automated testing, which is also the stage in which your script works.

Build a continuous integration environment based on Jenkins + GitHub