Jenkins + Maven + SVN + tomcat7 cluster deployment (1)

I read a lot of articles about cluster deployment on the internet, and I don't feel very consistent. Many of them just tell you how to install them, but there are a lot of problems encountered in the process, but it also solves many problems. I hope my article can help those who want to learn. Jenkins mainly solves a cluster project and node management tool, the project can be easily distributed to all containers, saving the need to put war packages in Tomcat one by one when the cluster is gone, and managing the status of a cluster node.

In fact, I like to practice theory first, so I will not say anything.

My environment is jenkins-1.569-1.1.noarch.rpm my advice is best to download this version, After all stable, before I went down the old version and a latest version, in the process of continuous error reporting. The system is a centos6.4 64-bit operating system. In fact, there is no big difference because it is in the form of war packages, shielding the differences between systems. There is also an official Windows installation package, but it is recommended that this version is more appropriate.

The first step is to install

<PRE name = "code" class = "plain"> rpm-IVH jenkins-1.569-1.1.noarch.rpm # Run this command to check whether the installation is successful after the installation is complete. If the following prompt appears, [email protected] FTP] # service Jenkins statusjenkins is stopped # Start Jenkins [[email protected] FTP] # service Jenkins startstarting Jenkins [OK]

At this time, the installation is successful. If it is local, you can access it through localhost: 8080. By default, it starts port 8080. Of course, this port can be changed.

VI/etc/sysconfig/Jenkins

Find jenkins_port = "8080" and modify the parameters.

Register

Jenkins

Service Startup

 

 

 

# Chkconfig Jenkins on

Register

Jenkins

Service Startup

 

 

 

# Chkconfig Jenkins on

Register Jenkins service for startup # chkconfig Jenkins on

If the above steps are successful, start our second step.

How to use:

If the local host is accessed through localhost: 8080

This is probably the interface, which can be used at this time, but is in the insecure stage. Anyone who knows the port and IP can obtain all the permissions, in this case, we need to manage users. First, we need to add a super administrator.

Choose System Management> Configure Global Security> and check the first option. The page appears.

Select the same option as the one on the image.

For project reasons, I select Project Matrix authorization mode and then add a super administrator.

Click "add", drag it to the rightmost side, and click the small icon to select all permissions. What are these permissions described in my theoretical article?

At this time, it will be added successfully, and then click "Save end Settings". When you access the system again, the page will appear.

At this time, you only need to register a user whose username is admin. Here, it corresponds to the user name where you add permissions.

The second article will be explained tomorrow, And MAVEN will be integrated with multiple Jenkins.

This is the final login interface