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
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?
Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events