What branch is the bitbucket-pipelines.yaml being loaded from? The main branch? Master? From the branch that it is supposed to build?
I have seen some strange behaviour where the bitbucket-pipelines.yaml has been modified in the main branch, but a scheduled build job has not picked up those changes.
For a working example, I have just committed the bitbucket-pipelines.yaml to a feature branch. There are no pipelines listed for the repository, I have also gone into the settings to enable pipelines which seems not to have made any difference.
What is the expected behaviour here? Does the bitbucket-pipelines.yaml file need to be committed to the default branch? Is this the first time only? If so I'd be concerned I can't test my changes before rolling them out to everyone.
Hey Community! We’re willing to wager that quite a few of you not only use Bitbucket, but administer it too. Our team is excited to share that we’ll be releasing improvements throughout this month of...
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