Execution Order of Queued Pipelines in Bitbucket Pipelines

[Zeljko Grubisic]

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.

[Syahrul]

G'daym @Zeljko Grubisic 

Welcome to the community!

I can see you have a paid workspace. Could you please open a support ticket with us and share the pipeline URL where you observe the queue pipeline starting in a random order?

You can submit a ticket through our support portal.

Thanks!
Syahrul

[Zeljko Grubisic]

Thank you for quick response!
Unfortunately, I can't share anything as all my repositories are private..
Also, I don't think this is a specific problem that I have, rather it's a default behavior of bitbucket pipelines.

[Syahrul]

Hi @Zeljko Grubisic 

Thank you for getting back to me. There may have been some confusion in our previous communication. I would appreciate it if you could raise a support ticket with us. This ticket will be accessible only to you and the support engineer assigned to it.

I’m interested in understanding the specific behavior you’re experiencing. Is it related to the pipeline steps queue, the runners, or something else? Reviewing your queue pipeline will help us better understand the issue.

If you’re open to exploring this further, please submit a support ticket through our support portal.

Regards,
Syahrul

[Krosan89]

@Zeljko Grubisic did you get any answer on your ticket? having the same issue

i found this https://jira.atlassian.com/browse/BCLOUD-16262 which indicates that it is not possible