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

Parallel Execution Of Cypress Automation Scripts Using Single Runner

I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 11, 2023

Hi Team - We are trying to achieve Parallel execution of our Cypress UI Automation Scripts using Bit Bucket. Tried to run our scripts in parallel but since we have only single self-hosted runner, only 1 step is getting executed and others are waiting in queue. 

So is there any way we can scale up the single runner? so that we would able to execute our automation scripts in parallel (Please note that since it will be difficult for us to register a bunch of duplicate runners looking forward for a solution on scaling up the single runner).

Request your inputs as this would help us to reduce our automation scripts execution time. 

1 answer

0 votes
Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 12, 2023

Hi Rajan and welcome to the community!

I'm afraid that this is not supported at the moment, a runner can run only one step at a time. It allocates the resources you provided to run your build, so when you have parallel steps it is queued up because the resources are currently used by one of the other steps.

The only way to run steps in parallel with a runner at the moment is by using multiple runners. In case you are using a Linux Shell, Windows, or MacOS runner, please keep in mind that deploying multiple runners to a single machine may lead to issues related to resource sharing/usage conflicts due to the shared build environment (the steps will not run in a separate Docker container as with Linux Docker runners, since these runners do not use Docker).

We have a feature request for allowing a single runner to run multiple steps:

I would suggest adding your vote in the features request (by selecting the Vote for this issue link) to express your interest, and also add yourself as a watcher (by selecting the Start watching this issue link) if you'd like to get notified via email on updates. Implementation of new features is done as per our policy here and any updates will be posted in the feature request.

Kind regards,

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events