Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Priority/order for which self-hosted runner to use?

Let's say I have 2 self-hosted runners available to build for my C++ projects.

One runner is on a server much more powerful than the other, so it finishes jobs faster. I'd like Bitbucket Pipelines to use this one when it's free, and only use the 2nd one on the rare occasions when the 1st is already running a job.

Is there a way to configure this, i.e. have Pipelines prioritize a runner over another? Or will Bitbucket Pipelines always randomly pick from the list of available runners?

1 answer

1 accepted

0 votes
Answer accepted
Patrik S Atlassian Team Dec 09, 2021

Hello @Fabregas4 ,

Thank you for reaching out to Atlassian Community!

At this moment, there's no option on Bitbucket Runners to configure the priority/order that a runner will be chosen when there are multiple runners available.

Currently, a build step configured to use runners will run on the next available runner that has all the required labels, with the following remarks :

  • If all matching runners are busy, your step will wait until one becomes available again.

  • If you don’t have any online runners in your repository that match all labels, the step will fail.

That being said, I went ahead and raised a feature request on our public issue tracker to add the functionality to set priority/order of runners, as you can see in the following link:

I would suggest you to add your vote there, since this helps both developers and product managers to understand the interest. Also, make sure you add yourself as a watcher in case you want to receive first-hand updates from that ticket. Please note that all features are implemented with this policy in mind:

Let us know if you have any other questions.

Best regards,

Patrik S

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events