[Turn] Jenkins Real-combat walkthrough of Windows System Node management

Premise

Through the "Jenkins real-combat walkthrough of Windows Server Rapid Build" (http://my.oschina.net/iware/blog/191818) and "Jenkins Practical walkthrough of the Linux Server Rapid Build" (HTTP/ my.oschina.net/iware/blog/191819) to complete the Jenkins Server Setup.

"Practical Walkthrough"

1) Log in to the Jenkins system as a registered user, select "System Management" > "Management Node";

2) After entering the node management interface, select "New node";

3) Fill in the node name, and select "Dumb Slave", click "OK" to enter the node parameter settings;

4) Set "# of Executors" to 1 (indicates that the node task executes 1 times), "Remote working directory" is "D:\". Jenkins "," usage "is" only allow jobs bound to this machine "," Startup Method "for" Launch slave agents via Java Web start ", click" Save "to set the parameters to save;

5) At this point, you can see that the "Windows (115)" Node status is not online;

6) Go to the "Windows (115)" Node link, download Slave.jar, and in the "D:\. Jenkins "Directory creation batch file" Launch.cmd "content is" Java-jar Slave.jar-jnlpurl http://10.10.100.110/computer/Windows (115)/ Slave-agent.jnlp-secret 949d0893801cc0719f5fa488585f5f250e325491ed3c56b8448d21fbdb442b6e "

7) Execute batch file "Launch.cmd", at this time can be seen through the console Windows node is connected, on the Jenkins at the same time to view the state of the node is idle, so we completed the Jenkins System of Windows node management, Later we can deploy the associated continuous integration job to that node.

Go The Windows System node management in Jenkins real-combat walkthrough