<p>I'm trying to trigger a job on my Jenkins for multiple times at the same time. But it looks like Jenkins is ignoring all builds I triggered when the very first build starts to run. </p>

<p>For example, in the screenshot below, I clicked the <code>builds start</code> button for 5 times with no delay. It is showing 5 builds on the queue as I expected.</p>

<p><a href="https://i.stack.imgur.com/S3Svi.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/S3Svi.png" alt="Jenkins build waiting list"></a></p>

<p>But once the job gets started after the executor (Kubernetes) becomes ready, the build queue suddenly gets cleaned up. Seems like the very first job I've triggered is only being executed, and the other queued jobs are just... gone.</p>

<p><a href="https://i.stack.imgur.com/eK2ZC.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/eK2ZC.png" alt="enter image description here"></a></p>

<p><a href="https://i.stack.imgur.com/lhcZc.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/lhcZc.png" alt="enter image description here"></a></p>

<p>I need to queue all jobs correctly for my use case. Is this a bug? Or is there something that I'm missing? How do I find a walkaround?</p>

<p>I'm running the latest <code>stable/jenkins</code> Helm chart on my Kubernetes v1.16.</p>

<p>Thank you.</p>

kycfeel
<p>In Jenkins, you've to set <code># of executors</code> value to a higher number if you need to run multiple parallel jobs. By default, it's zero. </p>

<p><a href="https://i.stack.imgur.com/aFOlB.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/aFOlB.png" alt="enter image description here"></a> </p>
