Frequently asked questions about Jenkins under Windows continuous integration

The so-called master-slave, the main application of scenarios such as multiple environments (windows/linux,.net/java/php) requires a different build base, and we do not want to have a series of steps and environment mixed on a build server, so similar to the Go agent, Jenkins also provides the concept of slave nodes, and you can deploy different types of projects to the node servers that are categorized. The node server does not need to install the full Jenkins package, and the distribution of build events is performed by the master.

Here need to pay attention to the communication between the master and subordinate nodes, I choose here will be from the node in Windows service to start, and I encountered the pit is the environment variable configuration problem, when I am in the master and subordinate services are installed JDK and configure the environment variables, found that the boot from the node or how can not find the JDK, card for half an hour to find Jenkins from the node's environment variables are required in the Web system configuration, the pit filled, the latter cautious.

As for the allocation of the slave end in the build configuration