OD-3118: Use FIFO when CI/CD job acquires resources

Use FIFO when CI/CD job acquires resources #3118

Ray Booysen opened 1 month ago

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.

Copy

Robin Shen changed title 1 month ago

Previous Value	Current Value
Change Queue Behaviour for Builds	Use FIFO when CI/CD job acquires resources

OneDev commented 1 month ago

State changed as build OD-8482 is successful

Copy
OneDev changed state to 'Closed' 1 month ago
Previous Value Current Value
Open

Closed
Ray Booysen commented 1 month ago

Thank you @robin

Copy
Login to comment

Previous Value	Current Value
Open	Closed

Type	Enhancement
Priority	Minor
Assignee	Robin Shen
Labels	No labels

Issue Votes (0)

Watchers (2)

Reference

OD-3118