Jenkins ignores multiple build triggering for the same job

0
votes

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.

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

Jenkins build waiting list

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.

enter image description here

enter image description here

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?

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

Thank you.

1
jenkinskubernetesautomationcontinuous-integration
What is your number of executors value? – hariK

1 Answers

1
votes

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

enter image description here