Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-53604

VMs are not provisioned if queue is populated with parallel pipelined jobs

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Major Major
    • google-compute-engine-plugin
    • None
    • Jenkins ver. 2.141
      Google compute engine plugin ver. 1.0.4

      If I trigger a pipeline job that fans out lots of different jobs in parallel via the jenkins pipeline command parallel, the created jobs will queue but won't trigger provisioning of new VMs. So what happens is that the job launches 50 parallel tasks which are queued with identifiers like "part of job-name #1234" and only one VMs will process them, instead of creating as many VMs as needed.

          [JENKINS-53604] VMs are not provisioned if queue is populated with parallel pipelined jobs

          Luca Naldini added a comment -

          It might be that the tasks were executed too quickly for the provisioning to happen. Will close for the time being

          Luca Naldini added a comment - It might be that the tasks were executed too quickly for the provisioning to happen. Will close for the time being

            evanbrown Evan Brown
            lucanaldini Luca Naldini
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: