Analysis of principle jenkins

Continuous Integration Continuous Integration (CI)

Schematic:

 

 

Gitlab as git server. Gitlab functions and Github almost, but is open source, can be used to build private git server, also provides a very powerful web GUI, such as developers review source code each time will be very convenient. Workflow system roughly divided into the following steps:

1 developer version of the new push to git server (Gitlab).

2 Gitlab then triggers jenkins master node once build. (Or timing detection by web hook)

3 jenkins master node will build this task is assigned to a plurality of registered slave node in this slave node according to a pre-set script build. This script can do many things, such as compile, test, generate test reports, and more. These would otherwise require manual tasks can be handed over jenkins do.

4 We build to be compiled, used here distcc a distributed compiler to speed compilation .

jenkins works is first copied from the source to the local copy of the gitlab then build according to the script provided. We can see, the key is that the whole system build script that tells the task in an integrated jenkins need to be performed.

But after I use Github as a git server. But actually similar.

 

The company is also using Subversion SVN is short, is a version control system open source

 

Guess you like

Origin www.cnblogs.com/betterquan/p/11635399.html