CODEWITHSUNDEEP
javawindowsjenkins
Richard Knop
Richard Knop

Reputation: 83755

Creating Jenkins Slave On Windows 2008 R2 Box

I have a master Jenkins server. I would like to create a slave Windows 2008 R2 slave Jenkins?

Do I need to install Jenkins on the slave box? Or is saving slave-jnlp file to disk and opening it enough?

I downloaded the slave-agent.jnlp and tried running it. I get:

enter image description here

Upvotes: 2

Views: 6202

Answers (3)

CodeShane
CodeShane

Reputation: 6510

This is because Java security related to jnlp has increased, preventing it from using http.

Option A) Secure method: Switch to HTTPS. Either buy and install a certificate, or even create your own Certificate Authority and self-sign your own certificate, install it, and install the CA as a trusted root on all nodes! Should work now.

Option B) Copy the slave-agent.jnlp file from the Jenkins server to the Jenkins node by some secure means, such as SSH, or for those who don't care about security (peer pressure, that):

wget http://10.150.0.150:8080/computer/NODENAME/slave-agent.jnlp

or via an administrative Powershell (also insecure transfer):

iwr('http://10.150.0.150:8080/computer/NODENAME/slave-agent.jnlp')

Set your Jenkins node to trust any insecure http that looks like it might be from your Jenkins server:

Windows > All Programs > Java > Configure Java > Security tab > Edit Site List
add your server ("http://10.150.0.150:8080", for instance)

double-click 'slave-agent.jnlp' file on desktop. Should see a Jenkins UI saying slave agent started.

File > Install as Windows Service

Highly recommend HTTPS (Option A.)

Upvotes: 0

Slav
Slav

Reputation: 27505

Well, which part of documentation did you follow? There are many ways of doing it

Upvotes: 0

Michael
Michael

Reputation: 2510

You don't install the full Jenkins server on the slave. Just the slave agent per this documentation: https://wiki.jenkins-ci.org/display/JENKINS/Distributed+builds#Distributedbuilds-Howdoesthiswork%3F

Upvotes: 1

Related Questions