Shulou(Shulou.com)06/02 Report--

This article introduces the knowledge of "how to build a continuous inheritance environment for jenkins". Many people will encounter such a dilemma in the operation of actual cases, so let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

Automatic construction

Https://my.oschina.net/u/2306127/blog/541222

Continuous integration

The core value of continuous integration is that any link in continuous integration is completed automatically without much human intervention, which helps to reduce repetitive processes to save time, cost and workload; continuous integration ensures that the code submitted by team members at each point in time can be successfully integrated. In other words, software integration problems can be found at any point in time, making it possible to release deployable software at any time; continuous integration can also be conducive to the development trend of the software itself. this is especially important in situations where requirements are unclear or change frequently. The quality of continuous integration can help the team make effective decisions and build team confidence in the development product.

Principles of continuous integration (excerpt)

The generally accepted principles of continuous integration include: 1) version control software is required to ensure that the code submitted by team members will not lead to integration failure. The commonly used version control software are IBM Rational ClearCase, CVS, Subversion, etc.; 2) developers must submit the code to the version control library in time, and must update the code locally from the version control library frequently; 3) there needs to be a special integration server to perform the integration build. According to the specific reality of the project, the integration build can be triggered directly by the modification of the software, or it can be started regularly, such as every half hour; 4) the success of the construction must be guaranteed. If the build fails, fixing errors in the build process is the highest priority. Once fixed, you need to start a build manually

Jenkins principle (integrated with maven,gitlab,tomcate continuous build)

Ln-s jdkXXX/ jdk-- Linxu soft connection

Jenkins deployment and Environment installation

Explanation of jenkins principle How to build a continuous integration environment through git, maven gitlab, tomcat jenkins deployment and environment installation jenkins project configuration and management principle 1 must get the source 1.1 I want to package from gitlab (source code private server) download the latest source code (TEst) 1.2 of the specified branch and locally switch to the past 2 run mvn clean install construction package 3 package and store the corresponding package to the finger location 4 to upload the corresponding package to our nexus private server (deploy, User and password) 5 dynamic deployment based on Tomcat. Jenkins deployment

Download https://jenkins.io/download/ to download two startup tests for the corresponding war package:

It can be started directly based on any servlet container (jetty\ tomcat), etc.

Start java-jar jenkins.war-- ajp13Port=-1-- httpPort=8888 based on java-jar command

About jenkins plug-in installation

First of all, select the plug-in recommended by default to complete the installation.

Go to the plug-in management page to install the following plug-in # maven management plug-in Maven Integration plugin # Container deployment plug-in Deploy to container Plugin build environment installation:

Server installs maven

Server installs git client

The workflow of the system is roughly divided into the following steps: 1 > developers transfer the new version of push to git server (Gitlab). 2 > Gitlab then triggers the jenkins master node to perform a build. The 3 > jenkins master node assigns this build task to one of several registered slave nodes (via web hook or timing detection). This slave node performs build according to a pre-set script. There are many things this script can do, such as compiling, testing, generating test reports, and so on. These tasks that need to be done manually can be left to jenkins. 4 > We are going to compile in build, where the distributed compiler distcc is used to speed up the compilation. Notes jenkins works by first copying a copy of the source code from gitlab to local, and then build according to the script you set up. As we can see, the key to the whole system is the build script, which is used to tell jenkins what tasks to perform in an integration. But I used Github as git server later. But in fact, it's pretty much the same. At this point, the focus and difficulty is still on the installation and configuration of jenkins.

This is the end of "how to build a continuous inheritance environment for jenkins". Thank you for reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.