![]() |
|
|
|
|
Issue Type:
|
![New Feature]() New Feature
|
|
Assignee:
|
Unassigned |
|
Components:
|
vsphere-cloud-plugin |
|
Created:
|
08/Dec/14 1:16 PM
|
|
Description:
|
Allow multiple VM names to be managed in a single vsphere plugin buildstep (such as stop / start).
IN context of using a Selenium grid farm that relies on a large number of Windows VM's to execute Webdriver tests, we want to use this plugin to stop & start the farm so that all the VM's are in a clean state before job execution on Jenkins. Typically there's one job that triggers execution of the Selenium test suite.
With the current plugin implementation , we have to define a long list of vsphere build steps (one for each VM in the farm) to be able to manage this.
Allowing multiple entries would simplify dramatically our setup.
|
|
Project:
|
Jenkins
|
|
Labels:
|
configuration
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Jurgen Van Bouchaute
|
|
|
|
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.
