|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
The funny thing is that another user has a similar problem - but their start failure is for slaves, not the build steps. Same problem in both cases; host or vCenter under load or taking longer than expected to complete the operation. Solution is the same in both cases: increase the timeout.
I hope to have a fix out for this in an official release in the next day or two.
By the way, you don't need a full vCenter to perform the work - you can talk directly to ESXi. It has to be a license ESXi; not the free one you can get from VMware. The free one won't accept SDK commands that the vSphere Plugin uses.