Parallel steps enable you to build and test faster, by running a set of self contained steps at the same time.
A way you might want to use this feature is:
- A single initial step to build the software
- A set of parallel steps to test your software:
- unit tests
- integration test
- browser test
- Deploying to multiple similar environments at the same time, for example:
- production environment in different parts of the world
- test environments that run different platform versions
All environments in a parallel step set must be of the same type, so don’t try to mix production and test environment types in the same set!
If you are doing a single build step leading to multiple parallel testing steps, then cache external build dependencies as much as possible in the first step, so you don't waste time doing it in each of your testing steps. Then run all your tests concurrently, they can use cache, and you'll get your results more quickly.
Configuring steps to run in parallel is easy, just indent the parallel steps:
pipelines: default: - step: # non-parallel step script: - ./build.sh - parallel: # these 2 steps will run in parallel - step: script: - ./integration-tests.sh --batch 1 - step: script: - ./integration-tests.sh --batch 2 - step: # non-parallel step script: - ./deploy.sh
Parallel steps can produce and consume artifacts. Things to be aware of:
- Parallel steps can only use artifacts produced by previous steps, not by steps in the same parallel set.
- Steps after the parallel set will get a combination of all files produced.
- If parallel steps produce artifacts containing a file at the same location, conflicts are resolved on a per-file basis, the files generated by latest step in the YAML file will win.
The image below shows how artifacts can be combined.
If you want to do some fancy logic in your scripts, the following variables are available during the parallel steps:
BITBUCKET_PARALLEL_STEP- zero-based index of the current step in the group, e.g. 0, 1, 2, …
BITBUCKET_PARALLEL_STEP_COUNT- total number of steps in the group, e.g. 5.
Be aware that the total number of build minutes used by a pipeline will not change if you make the steps parallel, but you'll be able to see the results sooner. The quicker you have the results, the quicker your iteration cycle can be.