Distributed building and deployment of Jenkins-nodes

Distributed building and deployment of Jenkins-nodes
1. What is the distributed build and deployment of Jenkins?

 

The distributed build of Jenkins is called a node in Jenkins configuration. Distributed build allows the same set of code or projects to be compiled and deployed in different environments (such as Windows and Linux systems.

Ii. When to use nodes and their functions

When we use multiple servers and configure tomcat or jboss cluster services, we can publish jenkins projects on different servers through jenkins node configuration (distribution of jenkins workspace, deploy the project to tomcat or jboss of different servers), which forms the distributed jenkins. Jenkins does not need to be installed on the node server (only one slave node service needs to be run). The distribution of building events is executed by the master (jenkins main service.

Requirements for a three-node Server

NOTE: If JDK does not exist on the node host, Jenkins automatically downloads the program. However, if Oracle restricts the automatic download of the program, the download will fail and the problem will continue to occur.

Suggestion: The environment paths of all Linux or Windows machines are uniform (for example, JDK and Maven). The installation location must be the same as that of the JDK and maven servers on which jenkins is located, that is to say, the JDK and Maven directories and file names on the server where jenkins is located and on each node server are the same. It is easy to manage and avoid problems.

Four-node Management

1. Create a node

　　

2. Configuration

　　

3. download and install the node service

　　

 

-- Click Launch to download the file as slave-agent.jnlp

-- Copy the slave-agent.jnlp file to the remote working directory D: \ jenkins9 on the remote server

-- Double-click to run the slave-agent.jnlp, if you run as expected, enter javaws D: \ jenkins9 \ slave-agent.jnlp In the cmd command

-- The running process is as follows:

　　

 

-- Click run:

　　

-- Connected is displayed, indicating that the node is successfully created.

 

4. Add this node to the service

After the window is closed or the computer restarts, the node is closed, so it is best to add this node to the window service.

Click the file menu in the window, and click Install as a service.

　　

 

Success example: (as shown in the red box)

　　
Summary

Because the various subsystems of itoo are distributed to different jboss servers to relieve the pressure on the servers, how can jenkins be used to continuously build the corresponding servers? This process has tried many methods, these include the use of jenkins deployment plug-ins to remotely deploy on other servers, but they are not successful. There are also many reasons, such as cargo problems (itoo does not involve cargo ), jboss version issues (the plug-in only supports jboss5 and jboss7 for itoo. However, it is best to find the node service provided by jenkins. As mentioned in this article, it is equivalent to the distributed construction and deployment of jenkins, and it is continuously built in concert with the current jboss service cluster.