I have no idea what the sCCL log lines are for. They're not from the vSphere Cloud Plugin, but maybe from another plugin.

The vSphere Cloud Plugin can start the VM (as you found), but getting the slave agent running can be a bit more tricky.

1) The Windows Service was unreliably in our environment, most likely due to our locked down machines and some bizarre parts of our network topography. Others have had used it to good effect. So your usage may vary.

2) The SSH approach will work. Windows doesn't have a native SSH server, but you can add them. I found that the Windows SSH servers don't always work perfect with the default Jenkins SSH slave starting, although it was possible to craft custom SSH commands that would work with the server. Although it can work, we don't use that approach because we have no static IP addresses in our environment, everything is DHCP driven.

3) My preferred method is the Java Web Start. It require a bit more manual work on the slave, but it works in our environment robustly. Simply put, all you have to do is have Java installed on the slave and somewhere, somehow, add a command to the slaves startup sequence. The command is simply "javaws http://YourJenkins/computer/SlaveName/slave-agent.jnlp" For Windows machines, I can put that in a CMD file that runs from the Startup Folder of a machine with AutoLogin enabled. Or a Scheduled Task. For Mac, a Startup Item that's an Automation Script. For Linux, a Login Item that runs a bash script that contains this command. Which ever way works for you.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Reply via email to