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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,466,080
Community Members
 
Community Events
176
Community Groups

Should you build and test in parallel steps in the pipeline?

If your build and testing steps do not depend on each other, is it best practice to use parallel steps in the bitbucket pipeline to increase efficiency? 

 

https://support.atlassian.com/bitbucket-cloud/docs/parallel-step-options/

 

What are some common patterns for this?

1 answer

0 votes

Hi Drew,

It's common to use parallel steps for deploying to multiple similar environments at the same time or for steps that perform tests. However, you could use them for build and testing steps if they don't depend on each other i.e. if your test steps do not need artifacts produced by the build steps. Parallel steps can only use artifacts produced by previous steps, not by steps in the same parallel set. So, if a testing step needs artifacts produced by a build step, then these two steps shouldn't be parallel.

Kind regards,
Theodora

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events