|
||||||||
|
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/d/optout.
It's been discussed - just allowing a cluster to be assigned. The problem is that there are more error cases that could occur. So far, we haven't added code to handle that case.
If you use the vSphere UIs to deploy, there's a number of validation checks applied during the selection process to ensure that you don't deploy to a wrong host that might be in a cluster. There's even logic that will force you to choose a host in the event that the cluster is not homogeneous. None of that logic would be duplicated in the vSphere plugin. That could allow for several failures to deploy for odd, cryptic, or just no good obvious reason. Classic example would be deploying a Mac VM to a cluster with UCS blades, or a UCS/Mac mix. By sticking to the resource, we're able to latch onto something definitive.
It's still possible - just more error prone.