-
Bug
-
Resolution: Won't Do
-
Minor
-
None
Using this plugin, the first job that starts instantly boots a new pod.
However, all other jobs that start while a job is already running first show the below two messages:
```
Still waiting to schedule task
Waiting for next available executor
```
Then, after a while, they eventually continue, and boot up a new pod as well.
How can I make all jobs instantly use new pods, instead of waiting for existing pods to become available?
- is blocked by
-
JENKINS-39933 Waiting for next available executor on any slave when using Pipeline
- Closed
- is related to
-
JENKINS-42184 Unable to run pods in parallel due to template nesting
- Closed