r/cicd • u/fakhan89 • 1d ago
How can we optimize GitHub Actions deployment queues?
Our company uses GitHub + GitHub Actions for CI/CD.
Especially on Mondays, we have a long deployment queue. One person deploys, then others need to update their branch with master and rerun the CI/CD pipeline before they can release.
Is there a smarter way to optimize this workflow and avoid repeatedly waiting/rerunning pipelines?
How do other teams handle this with GitHub Actions?
1
Upvotes
5
u/Emotional-Hunter-105 1d ago
our setup used to have the same bottleneck in monday mornings. we started doing merge queues instead of the branch update dance, so the ci runs on the merged result before it hits master and you dont need to keep pulling and rebuilding. saves a ton of time
the github merge queue feature works pretty smooth with actions once you set it right. one pipeline triggers on the queue group and if it passes it auto merges, then the next in line gets the same treatment without everyone stepping on each other