Hello, In my case, the machines that are being tested are Windows. A rough skeleton of the test process is: *) Tell the slave machine that it is time to start the test. *) Tell the slave machine the location of the .ISO file(s) it will use to re-install its OS. *) Slave machine installs a brand new OS from the .ISO(s). *) By now, the slave has broken communication with the Jenkins master. *) Slave machine reboots as part of the OS rebuild. *) At this point, we want the master to be able to tell the slave what tests to run, but the slave knows nothing about Jenkins.
So, how do we get that slave to "talk" with the Jenkins master again? Thanks in advance. Steve K. -- 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/6861676a-142c-437b-ac48-0795d2793925%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
