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
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
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?
What are some common patterns for this?
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.