Jenkins-windows node creation Deployment IIS Service

Now that you've just finished automating the Windows node service for the Jenkins platform, record the entire process here today to see

There are three steps in a big step:

One

The Jenkins platform joins the Windows node

This step I took a long time to study, I have a blog post, which describes the method of creating a Windows node, but I do not use its methods, do not know whether it can be successful, interested friends can self-test;

I'll give you a general description of my own testing process.

A. I first tested the online most described OpenSSH method, this method I test the result is the Jenkins Master node, can successfully connect to Windows from the node, but there are a lot of follow-up problems, please refer to my blog in the Windows Configuration OpenSSH service, this I have the opportunity to test A bit, a little reconciled, hehe (inside need a lot of coverage of the plug-in, please download it, I have already downloaded all, we better save up for later use)

B. I ended up using the launch slave agents via Java Web Start in Jenkins, where the next steps are to install the JDK on the Windows node, install git, add the executable files to the system variables, and click , generally install the JDK, and then execute the command of the Jenkins prompt under the cmd Command Connection service, and then start the download from the node, a dialog box, update, and then put this into a system service, the window file, click, inside an option, installed as a system of services, Install on the OK, so that the master and slave have been connected together;

Two

Create a new job inside Jenkins

Since my code is placed inside the Gitlab server in the intranet, (usually in git mode, the same is true for code management)

In the process of pull code, found that the total occurrence of/usr/bin/git can not initialize my node configuration path, this path is also problematic, my Windows installed Git location is: C:\Program Files\git\bin, I also configured this environment variable in the Windows node configuration, but the problem still exists, the final solution is in Jenkins's system Management system configuration, and then define a Git environment variable, that is C:\Program Files\git\bin, Start with a new git name, then in the job, call the GIT executable variable, select the created, and the code will succeed.

Three

The final configuration is simple, which is to open IIS in Windows, and then select the directory of the system, in the Jenkins build, you can choose the way Windows batch, call a location script file, you can, I replace the generated executable file directly with the executable path in the IIS configuration file, and then it's OK.

Test the way SSH, and then have a chance to add it, happy..........y, fix it.

Jenkins-windows node creation Deployment IIS Service