Jenkins has a master slave feature, Linux running jenkins is the master - Windows doing the build is a slave.
What you need to get working is the connection from the Windows slave to the master, since Windows does not really have support for SSH (not sure how far the powershell guys got) use the jnlp to get it up and working. See: https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+as+a+Windows+service#InstallingJenkinsasaWindowsservice-InstallSlaveasaWindowsservice%28require.NET2.0framework%29 if that does not work, all it really does is run the jnlp at boot which you can do vi powershell and scheduler thing in windows. At the moment you don't need any plugins. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/331fadbd-92ef-477f-af78-69cc9b4fc5ec%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
