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.
With this example of a bitbucket-pipeline.yml
pipelines: default: - step: script: - doA branches: '*': - step: script: - doB # we are here if default ran its steps (doA) successfully staging: - step: script: - doC # we are here if default and branches '*' ran their steps (doA then doB) successfully production: - step: script: - doC # we are here if default and branches '*' ran their steps (doA then doB) successfully
- doD
It doesn't behave as a pipeline (tasks in series) between the different conditions
- `default` is processed only if nothing else match. What would be more useful is a base step ran in all cases
- `branches: '*'` is ran only if there's no other branches conditions. What would be useful again is to run each matching condition, to be able to split the CI logic
Thanks for your efforts
ps: my previous post seems to have been marked as spam (https://community.atlassian.com/t5/Bitbucket-discussions/Process-matching-pipelines-stages-sequentially/td-p/826429), if that's really the case in this post, could you explain the reasons?