Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


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

How to see what jobs are running on Bitbucket pipeline Self-hosted runners

Hi, we have 2 self-hosted runners set up at the workspace level for a project. we have multiple (3) repos that are sharing the runners. Is there a view that allows me to see what jobs are running on each runner and what jobs are queued up? Since the runners are shared across repositories it's a bit hard to tell what's occupying the runner and preventing other pipelines from building. Also, with two runners does that mean we can have at most 2 steps running in parallel at the same time? 

1 answer

0 votes
Patrik S
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Apr 05, 2023

Hello @David Cheng ,

Thank you for reaching out to Atlassian Community!

I'm afraid that Bitbucket Cloud currently does not have an aggregated view of which pipeline is assigned to each runner at a given time. Currently, you would have to visit the pipelines page of each repository to confirm which of them have pipelines running. We do have a feature request opened to implement a dashboard to help visualize the usage of runners, which you can access at the following link : 

We encourage you to add your vote there and also mark yourself as a watcher to receive first-hand updates whenever there's any progress on the implementation of that feature.

As for your questions about parallel steps, each runner can run only one step at a time. In this case, if you have 2 runners, you would have a maximum of two steps running in parallel. When a step is triggered and no runner is available, the step will be queued until a runner completes its current step and becomes available.

Thank you, @David Cheng !

Patrik S

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events