-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
Jenkins: 2.263.4
Kubernetes-Plugin: 1.29.0
Kubernetes: v1.20.2+k3s1
With a `Concurrency Limit` (containerCap) limit set jobs queue as expected. However, as jobs finish the queued jobs do not execute in FIFO order. If I am not mistaken they appear to be executed in ASCII Sort of the job Name...
With a concurrency limit of 3, I kicked off 11 jobs (using the `Build Now` button) and they executed in the following order...
1,2,3,10,11,4,5,6,7,8,9
[JENKINS-64885] Queued Kubernetes destined jobs do not execute in FIFO order.
| Description |
Original:
With a `Concurrency Limit` (containerCap) limit set jobs queue as expected. However, as jobs finish the queued jobs to not execute in FIFO order. If I am not mistake they appear to be executed by ASCII Sort of the job Name...
With a concurrency limit of 3, I kicked off 11 jobs (using the `Build Now` button) and they executed in the following order... 1,2,3,10,11,4,5,6,7,8,9 |
New:
With a `Concurrency Limit` (containerCap) limit set jobs queue as expected. However, as jobs finish the queued jobs do not execute in FIFO order. If I am not mistake they appear to be executed by ASCII Sort of the job Name...
With a concurrency limit of 3, I kicked off 11 jobs (using the `Build Now` button) and they executed in the following order... 1,2,3,10,11,4,5,6,7,8,9 |
| Attachment | New: Screenshot 2021-02-16 134144.png [ 54012 ] |
| Attachment | New: Screenshot 2021-02-16 134702.png [ 54013 ] |
| Summary | Original: Queued Kubernetes destine jobs do not execute in FIFO order. | New: Queued Kubernetes jobs destine do not execute in FIFO order. |
| Summary | Original: Queued Kubernetes jobs destine do not execute in FIFO order. | New: Queued Kubernetes destine jobs do not execute in FIFO order. |
| Summary | Original: Queued Kubernetes destine jobs do not execute in FIFO order. | New: Queued Kubernetes destined jobs do not execute in FIFO order. |
| Description |
Original:
With a `Concurrency Limit` (containerCap) limit set jobs queue as expected. However, as jobs finish the queued jobs do not execute in FIFO order. If I am not mistake they appear to be executed by ASCII Sort of the job Name...
With a concurrency limit of 3, I kicked off 11 jobs (using the `Build Now` button) and they executed in the following order... 1,2,3,10,11,4,5,6,7,8,9 |
New:
With a `Concurrency Limit` (containerCap) limit set jobs queue as expected. However, as jobs finish the queued jobs do not execute in FIFO order. If I am not mistaken they appear to be executed in ASCII Sort of the job Name...
With a concurrency limit of 3, I kicked off 11 jobs (using the `Build Now` button) and they executed in the following order... 1,2,3,10,11,4,5,6,7,8,9 |
| Description |
Original:
With a `Concurrency Limit` (containerCap) limit set jobs queue as expected. However, as jobs finish the queued jobs do not execute in FIFO order. If I am not mistaken they appear to be executed in ASCII Sort of the job Name...
With a concurrency limit of 3, I kicked off 11 jobs (using the `Build Now` button) and they executed in the following order... 1,2,3,10,11,4,5,6,7,8,9 |
New:
With a `Concurrency Limit` (containerCap) limit set jobs queue as expected. However, as jobs finish the queued jobs do not execute in FIFO order. If I am not mistaken they appear to be executed in ASCII Sort of the job Name...
With a concurrency limit of 3, I kicked off 11 jobs (using the `Build Now` button) and they executed in the following order... 1,2,3,10,11,4,5,6,7,8,9 !Screenshot 2021-02-16 120906.png|thumbnail!!Screenshot 2021-02-16 121045.png|thumbnail!!Screenshot 2021-02-16 121133.png|thumbnail! |
(see screen grabs...)
with a queue of
I would expect zzz3 to be picked up next.. however, aaa 2, aaa 3, aaa 4 were executed before zzz 3... etc.