Problem: Currently, Bitbucket pipelines executes queued pipeline steps in a random order, which can lead to later triggered pipelines running before earlier ones. This lack of control can cause inconsistencies.
Example:
- Two pipelines are triggered on the master branch, with IDs #100 and #101.
- Both pipelines ends up in queue.
- Pipeline #100 should finish before pipeline #101, but due to the current random execution order, pipeline #101 might start and finish before pipeline #100.
It would be great if you could introduce a feature to control the execution order of queued pipelines, ensuring that pipelines are run in the order they were triggered.
This feature could be configurable on a repository and workspace basis.
