When new builds are placed in the queue, it seems the standard behaviour is LIFO. Imagine a setup where if we create a PR, 10 builds are queued. I can reproduce this by pushing PR 1, this kicks off the builds, maybe 5 builds running, 5 scheduled based on the # of builds we can run.
If we then push PR 2, OneDev will prioritize PR 2's builds. This causes longer waiting times for PR 1, which should, in my opinion, should be a FIFO queue as older PRs should be merged first.
Alternatively if there was config to change the queuing behavior, that also would be helpful.
When new builds are placed in the queue, it seems the standard behaviour is LIFO. Imagine a setup where if we create a PR, 10 builds are queued. I can reproduce this by pushing PR 1, this kicks off the builds, maybe 5 builds running, 5 scheduled based on the # of builds we can run.
If we then push PR 2, OneDev will prioritize PR 2's builds. This causes longer waiting times for PR 1, which should, in my opinion, should be a FIFO queue as older PRs should be merged first.
Alternatively if there was config to change the queuing behavior, that also would be helpful.