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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
For a bitbucket-pipelines like this:
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
I'd expect that default is ran every time, whatever follow (currently it's not the case, default is only ran if there's nothing else matching)
I'd also expect that each matching branches pattern are ran, in order (currently only last one is ran)
You could add a mode: sequential in the pipelines root properties, or at least a `shared` property under pipelines, ran in all cases
"Pipeline" in Computing means a set of tasks connected in series, that's why the current behavior is confusing
It'd be possible to put everything under `default` and use `BITBUCKET_BRANCH` case conditions, but that's not very readable and not easy in yaml
note: the html editor is not working well with code and pasting, Ii had to format this post from the dev console `$0.textContent = `pipelines:...`