You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
In a Runner setup the following steps don't run in parallel. One will run and the other is queued.
pipelines:
custom:
customPipelineWithRunnerStep:
- parallel:
- step:
name: Build 1
size: 2x #8 GB
runs-on:
- 'build'
- 'test'
- 'self.hosted'
- 'linux'
services:
- docker
caches:
- docker
- dotnetcore
script:
build.sh
- step:
name: Build 2
size: 2x #8 GB
runs-on:
- 'build'
- 'test'
- 'self.hosted'
- 'linux'
services:
- docker
caches:
- docker
- dotnetcore
script:
build.sh
G'Day!
Each step uses one runner that has been configured. If you run parallel steps, you are running multiple steps at the same time so it will look for all available runners.
However, if you only have one runner configured then this will cause the parallel step to queue up because it's waiting for the first steps to complete so it frees up the runner. This will repeat each parallel step until all steps are complete.
If you wish to have all parallel steps run together then you'll have to add more runners. For example, you have 5 parallel steps, you need to add 5 runners so that when the parallel steps run it has 5 available runner resources.
I hope this clarifies, let me know if you have any additional questions.
I hope this clarifies.
Cheers,
Syahrul
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.