![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Affects Versions:
|
current |
|
Assignee:
|
Unassigned |
|
Components:
|
vsphere-cloud |
|
Created:
|
30/Jan/14 8:58 PM
|
|
Description:
|
This only happens when more than one vSphere Cloud is configured on the system. If a vSphere Build Step in a job is configured to use a cloud other than the first (default) one and the job is saved - the correct vSphere Cloud is saved with the job. Running the job will show that the correct vSphere Cloud was used.
Configuring the job and going to the vSphere Build Step will show that the vSphere Cloud is now reset to the first (default) one. Saving the job will set this new Cloud. If you cancel from the configuration, the original Cloud value is still saved.
|
|
Environment:
|
Jenkins 1.549, vSphere Cloud 1.1.3
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Critical]() Critical
|
|
Reporter:
|
Jason Swager
|
|
|
|
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/groups/opt_out.
