Catalog

Abstract :

jenkins working principle ：

master Nodes and agent Node description :

Explanation of node diagram and sequence diagram :

Deploy :

Deploy jenkins(master node ):

Deployment environment :

Deployment steps :

matters needing attention :

Deploy agent node :

Deployment environment :

Deployment steps :

matters needing attention :

Abstract :

Use jenkins Do internal ci, The reason lies in jenkins The simplicity and process coding and documentation are convenient for version control and tracking of the process itself .

This article explains how to deploy jenkins Of master Nodes and agent node

jenkins working principle ：

master Nodes and agent Node description :

1. master node : namely jenkins Service itself , By default 8080 Port starts a website service
2. agent node : Actual work node , Accept master Tasks distributed by nodes , Return the result to master. All the assembly lines are agent Node operation .

Explanation of node diagram and sequence diagram :

explain :

1. User opened jenkins The web page is master node , The user to master Node triggers task
2. master The node distributes the task to the matching tag agent node , By matching labels agent The node performs specific tasks pipeline
3. agnet The node returns the execution result master node , master The node displays it to the user on the page

Deploy :

Deploy jenkins(master node ):

Deployment environment :

1. unlimited , windows Or any linux Release versions are available

Deployment steps :

With linux For example :

Linux

Redhat Jenkins Packages

matters needing attention :

1. Deploy master My machine as jenkins Service itself , Make sure the machine is stable
2. Need to jenkins The service is added to the startup service , For convenience jenkins Self healing of services

Deploy agent node :

Deployment environment :

1. In which environment does the task to be executed run , will agent In which environment is the node's service deployed
2. for example :

1. 1. test stonedb stay centos compile , will agent The service is in the corresponding centos Start on Service
   2. Other environments are the same

Deployment steps :

One . Make sure the agent String of tags , You need to determine one first , To make it easier to find , The rule is : agent-ip Address

Two . open jenkins Website , Find the node add page , for example http://192.168.30.238:8080/computer/new, Copy existing nodes directly

3、 ... and . Change to yourself agent The name of i In and labels and working directories

Four . Save the page , Appears for starting agent Commands for services , In the corresponding agent Use this command on the machine to start the agent service

Normal startup log :

Jul 11, 2022 6:26:56 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Handshaking
Jul 11, 2022 6:26:56 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Connecting to 192.168.30.238:5549
Jul 11, 2022 6:26:56 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Trying protocol: JNLP4-connect
Jul 11, 2022 6:26:56 PM org.jenkinsci.remoting.protocol.impl.BIONetworkLayer$Reader run
INFO: Waiting for ProtocolStack to start.
Jul 11, 2022 6:26:57 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Remote identity confirmed: 7f:16:6a:5a:af:09:4c:97:39:8e:ad:3f:f6:5c:c7:20
Jul 11, 2022 6:26:57 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Connected

5、 ... and . View the launched agent Node services

http://192.168.30.238:8080/computer/

matters needing attention :

1. agent The label of is used for subsequent jenkinfile Pipeline file use , Need to be careful
2. agent It is better to add the start-up service to the service of the node , In order to restart the machine agent Node service self-healing