-
New Feature
-
Resolution: Unresolved
-
Minor
-
None
This will help in deploying appliance which are in ova/ovf format.
Also provide an option to edit CDROM settings of a VM.
Both of these will help in test automation.
[JENKINS-35371] Please add option to deploy ova file using vSphere Cloud Plugin
pjdarton
added a comment - These are two independent enhancements - the CDrom stuff would probably be an enhancement to the "reconfigure VM" build step.
As for ova/ovf stuff, that really doesn't fit with the way vSphere & Jenkins communicate, e.g. what would "host" the ova/ovf files to provide them to vSphere? They'd really need to already be on the vSphere server to start with ... and if an end-user is able to arrange for that, they can also turn that into a vSphere template that vSphere is then able to use ... and which this plugin is able to tell vSphere to use.
FYI there is no "ETA" on this because nobody seems to want it badly enough to implement support for it. This is free open-source software and you "get what you pay for" 
If you (or anyone else who wants this) can come up with a good design for how this would fit into the existing plugin functionality and, ultimately, create a pull-request that implements it, I'd be willing to help review the design/implementation and merge it into the code (as long as the demands on my time are kept to a minimum).
pjdarton
added a comment - These are two independent enhancements - the CDrom stuff would probably be an enhancement to the "reconfigure VM" build step.
As for ova/ovf stuff, that really doesn't fit with the way vSphere & Jenkins communicate, e.g. what would "host" the ova/ovf files to provide them to vSphere? They'd really need to already be on the vSphere server to start with ... and if an end-user is able to arrange for that, they can also turn that into a vSphere template that vSphere is then able to use ... and which this plugin is able to tell vSphere to use.
FYI there is no "ETA" on this because nobody seems to want it badly enough to implement support for it. This is free open-source software and you "get what you pay for"
If you (or anyone else who wants this) can come up with a good design for how this would fit into the existing plugin functionality and, ultimately, create a pull-request that implements it, I'd be willing to help review the design/implementation and merge it into the code (as long as the demands on my time are kept to a minimum). 
Seem very old issue. any ETA on this ?