I just want to be sure about something that doesn't sound so great to me :
I have my bitbucket-pipelines.yml in my dev branch, but does it need to be in every other branch ? I've set it so it triggers a pipeline on every pull-request, but for every old branch that doesn't yet have the file, nothing is triggered. Is this normal behaviour ?
What scares me a bit, if that's the case, is how are you supposed to manage your pipelines properly ? Like every time you update it, you have to manually propagate that to other branches ?
Thanks for your help.
This is correct. The bitbucket-pipelines.yml file must be in the specified branch in order for it to be run.
The expectation is that branches remain (roughly) in sync. Such as with a feature branching workflow.
What is your branch workflow out of curiosity? Is there a reason you can't keep your branches in sync regularly?
...hey are a part of us, shaping how we interact with the world around us. The same holds true for programming languages when we think about how different kinds of vulnerabilities raise their heads in t...
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