Bitbucket Pipelines not triggering builds for specific branches
Platform Notice: Cloud - This article applies to Atlassian products on the cloud platform.
Summary
After performing a push, or merging to a specific branch, Pipelines is not triggering a build, despite the YAML file containing a section for that branch name.
Environment
This article is related to Bitbucket Cloud and Bitbucket Pipelines only.
Cause
This happens since Git is case-sensitive when it comes to branches' names, so Bitbucket Pipelines YAML validator will also take this case sensitivity into consideration. If the branches are created using upper or lower case characters, they must match the branch name inside the YAML file, otherwise the build will fail to be triggered.
Solution
In order to solve this problem, you can either:
- Edit your YAML file so that the branches' names match; or
- Rename your branch to match the syntax in the YAML file.