当前位置：网站首页>Yunyuanyuan (IX) | Devops chapter Jenkins installation and actual combat

Yunyuanyuan (IX) | Devops chapter Jenkins installation and actual combat

2022-07-22 02:27:00 【InfoQ】

One 、Jenkins install

1、 background

Jenkins, It used to be called Hudson, from SUN The company started ,2010 year oracle Acquisition SUN Lead to hudson The trademark belongs to oracle Retain ,hudson Our main contributors are based on hudson Renamed jenkins And keep updating . For a long time lenkins and Hudson Continue as two separate projects , Everyone thinks of each other as their own branch . at present Hudson Development has stopped , The latest version was released in 2016 year , and Jenkins Our community and development are very active .Jenkins It is the most used in the market at present CICD Tools .

Jenkins Is based on Java A continuous integration tool for development .

Jenkins As a continuous integration tool , Continuous integration is its core function , On the basis of core functions, it can be extended to realize powerful CD function .

2、 characteristic

Free open source

Easy to install ( Basically all CI The simplest installation and configuration in the tool )

Multi platform support (windows/linux/macos)

Master slave distributed architecture

Provide web Visual configuration management page

Simple installation and configuration

Plugins are rich in resources

3、 Official website installation document address

https://www.jenkins.io/zh/doc/book/installing/

You'd better look at the official website documents for installation , Good open source software is generally well written on the official website , Otherwise it's hard to get angry .

This is mainly for demonstration docker Mode to install Jenkins, No installation docker Or don't know docker How to install students can first look at my article 《

https://lansonli.blog.csdn.net/article/details/124202180

【 Cloud native | Docker piece 】 Learn principles easily ｜ framework ｜ install ｜ Speed up （ One ）

》, installed docker Then look down

4、 Start installation

Be careful ：

jenkinsci/jenkins It's not blueocean The plug-in , You have to pretend

jenkinsci/blueocean： Yes

 # Build your own image RUN Set the time zone when you need to  # If it's someone else's mirror ,docker hub,UTC; Container runtime , -v /etc/localtime:/etc/localtime:ro

docker run \
-u root \
-d \
-p 8080:8080 \
-p 50000:50000 \
-v jenkins-data:/var/jenkins_home \
-v /etc/localtime:/etc/localtime:ro \
-v /var/run/docker.sock:/var/run/docker.sock \
--restart=always \
jenkinsci/blueocean

#/var/run/docker.sock Express Docker The daemons are based on Unix Socket . This mapping allows jenkinsci/blueocean Container and Docker Daemon communication , If jenkinsci/blueocean The container needs to instantiate other Docker Containers , Then the daemons are required . If you run declarative pipes , Its syntax includes agent Partly with docker; for example , agent { docker { ... } } This option is required .

# If your jenkins The plug-in cannot be installed . Use this image 【 registry.cn-qingdao.aliyuncs.com/lfy/jenkins:plugins-blueocean 】 Default access account / The password is 【admin/admin】

 5、 Installing

6、 installation is complete

7、 Page access

8、 Find the password with the following command

Mode one ：

Mode two ：

9、 Install the default recommended plug-ins , And configure the user

Select the recommended plug-in installation option

Just wait for the automatic plug-in installation to complete

Configure users , Click the lower right corner to save

installation is complete  

Two 、

Jenkins actual combat

1、 Prepare one git Project to test

We use

gitee

For example ,

github

Maybe it's too slow . need idea install gitee plug-in unit . Or you can be familiar with manual commands .

Briefly , Actually, it's used here

gitee、github

Or use

gitcode

Can be achieved , Which one to use , Students can choose by themselves

step ：

idea establish Spring Boot project

VCS - establish git Warehouse

gitee Create a warehouse , Upload locally to the warehouse

idea Submit content to gitee

Develop the basic functions of the project , And create a... In the project jenkinsfile file

Create a file called devops-java-demo Assembly line project , Use the project's own pipeline

Jenkins workflow

First define a pipeline project , Specify the git Location

Pipeline start

1、 Go first git Position auto pull code

2、 Analyze the... In the pull code Jenkinsfile file

3、 according to Jenkinsfile Start processing the project with the specified pipeline

Not very good at writing pipeline configuration files. You can refer to the official documents , Very detailed  

Description document of the pipeline on the official website ：

Assembly line

Jenkins Important point
1、jenkins Home directory /var/jenkins_home It has been docker Externally mounted  
/var/lib/docker/volumes/jenkins-data/_data
2、WORKSPACE（ working space ）=/var/jenkins_home/workspace/java-devops-demo
Every assembly line project , Occupy a folder location
BUILD_NUMBER=5; How many times are you building
WORKSPACE_TMP（ Temporary directory ）=/var/jenkins_home/workspace/[email protected]
JOB_URL=http://192.168.88.163:8080/job/java-devops-demo/

3
、 If there is no common environment ,jenkins Configuring the environment involves a lot of operations

4、jenkins_url ：
http://192.168.88.163:8080/

Small case test ： 

//  Write pipeline script （ declarative 、 Scripted ）
pipeline{
 //  All of the CICD Processes need to be defined here 

 //  Any agent available can execute 
 agent any

 //  Define some environmental information 

 //  Define the processing flow of the pipeline 
 stages {
 //  All stages of the pipeline 
 // 1、 compile 
 stage(' compile '){
 steps{
 //  Everything to do 
 echo &quot; compile ...&quot;
 }
 }

 // 2、 test 
 stage(' test '){
 steps{
 //  Everything to do 
 echo &quot; test ...&quot;
 }
 }

 // 3、 pack 
 stage(' pack '){
 steps{
 //  Everything to do 
 echo &quot; pack ...&quot;
 }
 }

 // 4、 Deploy 
 stage(' Deploy '){
 steps{
 //  Everything to do 
 echo &quot; Deploy ...&quot;
 }
 }
 }

2、

Remote build triggers

Expected effect ：

The remote github The code is submitted ,jenkins Pipeline automatically triggers construction .

Implementation process ：

1、 Guarantee jenkins The host can be accessed remotely

You can configure a public network on the cloud platform IP, Give Way gitee Remote access to

2、jenkins Permission is required for medium and remote triggering , We should use users for authorization

3、 To configure gitee/github,webhook Trigger

Test success

  The first two errors are because my address is not used API Token, The following figure shows how to generate Token Set up

 # Remote build even if configured github Of webhook, Default meeting 403. We should use users for authorization
1
、 Create a user
2
、 Be sure to log in and activate it at random
3
、 Generate a apitoken
http://cheshi:[email protected]:8080/job/simple-java-maven-app/build?token=lansonli

Remote trigger ：

JENKINS_URL

/job/simple-java-maven-app/build?token=

TOKEN_NAME

The request can be

Submit directly later push The code triggers an automatic build , You don't have to trigger it manually

Test the officially recommended gitcode Whether it also supports this function

I use Alibaba cloud servers , Again

Jenkins,

Here are my test results , In fact, it can be used

1、 Copy the above test code and submit it to gitcode, If you don't know how to use gitcode Take a look at the official tutorial

2、 To configure

webhook Trigger

Some people say that apitoken What about the generation process , I'll just skip , Because it's written in detail , Don't take up space to write it again