The distributed construction and deployment of Jenkins--node

What is Jenkins's distributed build and deployment

The distributed build of Jenkins, called nodes in the Jenkins configuration, enables the same set of code or projects to compile, deploy, and so on in different environments (e.g. Windows and Linux systems).

Two when to use nodes and functions

When we use multiple servers and have Tomcat or JBoss Cluster service configured, the Jenkins Project can be published on different servers through Jenkins's node configuration (distributing the Jenkins workspace, deploying the project to different server Tomcat or JBoss), This forms the distribution of Jenkins. Node servers do not need to install Jenkins (only one slave node service is required), and the distribution of build events is performed by the master side (the Jenkins Master Service).

requirements for three-node servers

Note: If Jdk,jenkins does not exist on the node host, it will download automatically, but Oracle restricts the automatic download of the program, causing the download to fail and then cycle through the problem.

Recommendation: The environment path for all Linux or Windows machines is uniform (e.g. JDK, maven), the installation location and the JDK and maven of the server where Jenkins must be consistent, This means that the JDK and MAVEN directories and filenames are the same on the server that Jenkins is on and on each node server. Easy to manage, not prone to problems.

Four node Management

1. New node

　　

2. Configuration

　　

3. Download the Installation node service

　　

-- Click Launch to download the file for SLAVE-AGENT.JNLP

--Copy the SLAVE-AGENT.JNLP file to remote working directory D:\JENKINS9 of the remote server

--double-click Run SLAVE-AGENT.JNLP, enter javaws in the cmd command if you are running as normal D:\JENKINS9\SLAVE-AGENT.JNLP

--The running process is as follows:

　　

--Click to run:

　　

--Displays connected, which indicates that this node was created successfully.

4. Add this node to the service

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

Click on the File menu in the window and click Install as a service to complete

　　

Success Example: (shown in the red box)

　　

Five Summary

　　Because Itoo subsystems are distributed to different JBoss servers to relieve the pressure on the server, how to build the server through Jenkins, this process tries many ways, including deploying plugins using Jenkins to deploy to other servers remotely. However, there are many reasons for this, such as cargo (Itoo did not involve cargo), JBoss version of the problem (plug-ins only support Jboss5,itoo JBOSS7) and so on. But it's best to find the node service provided by Jenkins, which, as this article says, is equivalent to the distributed build and deployment of Jenkins and is continuously built with the current JBoss service cluster.

The method is always more than the problem, the more extension some will have the new discovery.

The distributed construction and deployment of Jenkins--node