Jenkins introduction

1、 Introduction to continuous integration

         Continuous integration Continuous integration , abbreviation CI With the increasing complexity of software development , How can team members work better together to ensure that the software The quality of development has gradually become an unavoidable problem in the development process . Especially in recent years , agile （Agile） More and more popular in the field of software engineering , How to quickly adapt to the changing needs and ensure the quality of software is also important It's especially important . Continuous integration is a kind of software development practice aiming at this kind of problem . It advocates that team development members must often Integrate their work , Even multiple integrations can occur every day . And every integration is built through automation To verify , Include automatic compilation 、 Release and test , To find integration errors as quickly as possible , Let the team drive faster Send cohesive Software .

2、 Continuous integration has the characteristics of

         It's an automated, periodic integration testing process , Check out code from 、 Compiling and constructing 、 Run the test 、 result Record 、 Test statistics, etc. are all done automatically , No manual intervention required ; A dedicated integration server is needed to perform integration builds ; Need code Managed tool support , In the next section, we will introduce Git And visual interface Gogs Use

3、 The role of continuous integration

         Ensure the quality of code submitted by team developers , Reduce the pressure of software release ; Any part of continuous integration is done automatically , There is no need to Too much manual intervention , Helps reduce duplication Process to save time 、 Cost and workload ;

4、 The use principle of continuous integration

        1. Code submitted by members of the version control software assurance team will not lead to integration failure , Commonly used version control software cvs,subversion,git etc.
        2. Developers must submit code to the version Library in time , You also need to update the code from the version library to the local frequently
        3. The development environment should be unified , for example JDK Version of , Tomcat The version of
        4. The frequency of integration should be appropriate , Cannot be less , Not too much , It is recommended to integrate twice a day

5、Jenkins brief introduction

        Jenkins, Original name Hudson,2011 Changed its name to its present name , It is an open source implementation of continuous integration Software tools . Official website ：http://jenkins-ci.org/. Jenkins Be able to implement errors in monitoring integration , Provide detailed log files and reminders , You can also use pictures The form of table vividly shows the trend and stability of project construction .
        Jenkins Is an open source continuous integration tool , Use Jenkins Build a continuous integration environment , It can be built automatically 、 Automatic compilation and automatic deployment , Very convenient . It provides an easy-to-use continuous integration system , Free developers from complex integrations , Focus on more important business logic implementation . meanwhile Jenkins It can also monitor the errors in the integration , Provide detailed log files and reminders .

characteristic ：
         Easy to install ： Just one. java -jar jenkins.war, After downloading the file from the official website , Direct operation , No amount required Installation of external , There is no need to install the database ; 
         Easy to configure ： Offer friendly GUI Configuration interface ; 
         Change support ：Jenkins From the code warehouse （Subversion/CVS） Get and generate a code update list in Output to compile output information ; 
         Support permanent links ： The user is through web To visit Jenkins Of , And these web The link address of the page is Permanent link address , therefore , You can use this link directly in various documents ; 
         Integrate E-Mail/RSS/IM： When an integration is completed , These tools can tell you the integration results in real time （ According to the What I know , Building an integration takes time , With this function , You can wait for the results in , Do something else ）;
        JUnit/TestNG Test report ： That is to provide detailed test report functions in the form of charts ; 
         Support distributed build ：Jenkins Integration building and other work can be distributed to multiple computers ; 
         File fingerprint information ：Jenkins Which integration builds will be saved and what results jars file , Which integration build makes Which version did you use jars Documents and other construction records ; 
         Support for third-party plug-ins ： bring Jenkins Become more and more powerful .

Here are the USES Jenkins Some of the reasons ：
    1. It's all CI The simplest of the products in terms of installation and configuration
    2. be based on Web visit , The user interface is very friendly 、 Intuitive and flexible
    3. Lots of plug-ins . These plug-ins greatly extend Jenkins The function of , They are all open source
To put it simply ,Jenkins It's just one. Web Applications , The function of this program is to provide all the functions required for continuous integration .