Feature: Sequential Build and Deploy Queue System #6910
Description
🔖 Feature description
Add functionality to queue and process git commits sequentially, ensuring that only one commit is built and deployed at a time. When multiple commits are detected, they should be queued and processed one-by-one, with each subsequent build/deploy starting only after the previous one completes (either successfully deploying to the next stage or failing).
🎤 Pitch / Usecases
The primary usecase is blame and debugging. If we can see where it first failed, right now there could be many commits to check, but with this new system, it would be only one commit, and that commit can be reverted so that it does not hold back other features from proceeding.
🔄️ Alternative
Currently, there is no built-in way to enforce this behavior in Devtron. Teams would need to manually control commit flow or implement external tooling to prevent concurrent commits from being detected simultaneously.
👀 Have you spent some time to check if this issue has been raised before?
- I checked and didn't find similar issue
🏢 Have you read the Code of Conduct?
- I have read the Code of Conduct