Jenkins Configure distributed Deployment

This is the configuration summary of Jenkins after installation. For reference only

Login jenkins,http://localhost:8080

Jenkins needs to configure the login rights and nodes of Jenkins after new completion;

First, increase the login rights:

1. Modify Jenkins to enter a username and password to log in;
   

2. Click on the left side of the system management-user management-Create a new user, set up a user to reopen the Jenkins URL, click the login button in the upper right corner to login, non-login mode, only to view the Jenkins configuration, can not make any changes.

Second, increase the node

1. Click on the left side of the system Management-management node-new node, enter the name of the node, it is recommended to use sever name such as: demo, late convenient to distinguish, select Dumb Slave Click OK.

2. Enter Slave's Jenkins working directory, such as:/var/lib/jenkins/;

3. The protocol defaults to the IP address of the Ssh,host server, click Add to add the server's user rights (recommended to use non-root users). Click Save to save the exit.

4. After the node is configured, you need to test connectivity, click on the new node in the Management node--lanuch save agent, check for errors, there are two kinds of error message: First, the Jenkins working directory is not correct; second, the server user name password is not correct;
   

5. Once the node is configured, start building the first task.
   

Click the New button on the left to create the first task.

Enter a name for the Ltem project, enter a name for the purpose of the project, such as: Demo-web. For a more flexible configuration of building content, it is recommended to "build a free-style software project".

Select "Parametric build process", according to the content of the project to fill different building parameters, program building process needs to connect to GitHub, in the first line to fill in the proxy address and port.

Source management for the GitHub code base address: URL format: [email protected]:* **.git, click Add to add GitHub privileges.

Third, distributed deployment

1. Distributed deployment only needs to replicate the Jenkins working directory to other servers

2. Configure the method to refer to "adding node content".
   

Jenkins Configure distributed Deployment