VMs will be started until a job is waiting in the queue

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major
    • Component/s: vsphere-cloud-plugin
    • None
    • Environment:
      jenkins 1.466, vsphere-cloud 0.10, several esxi instances

      I have several ESXi instances in my environment with VMs on it which I need only for testing. I have also several jobs which triggers the tests. because I have very different technologies and because I do not want to maintain all VMs with all technologies I have labeled the VMs and also the jobs. So some jobs can be executed everywhere, some others only on specific VMs.

      The problem is that a waiting job in the queue triggers the deployment of all VMs currently not in use. If the job cannot be executed on these VMs a loop of deploying and undeploying VMs will be triggered until the job will be handled by an executor.

      Suggestion for a solution:
      Before a VM gets deployed it should be checked if the labels will allow an execution on this executor.

            Assignee:
            Unassigned
            Reporter:
            Thomas Fürer
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: