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.