Hi,
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.
Malik
Hello,
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?
Thanks,
Phil
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.