Jenkins's windows slave distributed build and deployment

1, the new slave: System Management--"Management node--" New node

Remote working directory is the node server site file directory

Launch Agent via Java Web start cannot find this option in the option to start the method configuration when the node is configured

The reason for this is that TCP port for JNLP agents this item is not selected randomly selected

Workaround:

System Setup--"Configure Global security--" TCP Port for JNLP agents

2, after the new node appears as the interface:

Click the launch button to download a SLAVE-AGENT.JNLP file, and copy the file node server to run the installation, install the SLAVE-AGENT.JNLP before installing the JDK environment on the node server, as to how to install the JDK here is not explained, many online tutorials, the following installation of SL AVE-AGENT.JNLP, double-click the SLAVE-AGENT.JNLP file and the interface appears:

Click on the Run button to install successfully such as interface

3, refresh the interface, you will find that the red X is missing, and the node server has been connected to the

4. Start new (job) to build and deploy

5. Configure the General Options tab RESTRICT where this project can be run

6, fill in the Build Environment option (tab) Copy data to workspace, this option is to copy the file specific path, that is, the site's file path

7. Configure post-Build Action options (tab) Email notification configuration

After the build is successful, the message is sent:

Mail send after build failed

Configuration has been completed click the Save button appears as the interface complete configuration

8, configuration to this has been configured to complete, the next step is to start building the

9. Build Success:

Build (copy) to a site file on a node server

To this build complete

This blog has the correct place, hope you greatly generous enlighten, many comments

Jenkins's windows slave distributed build and deployment