Committing a change to the master branch does not trigger a pipeline build

[Robert Voorn @ Developers.nl]

I have the master in the bitbucket-pipelines.yml repository master, but commits do not trigger a pipeline build. Can someone help me with this?

[davina]

Hi Robert,

Some common reasons a pipeline may not be triggered when expected are:

Your bitbucket-pipelines.yml file is invalid

You can check this by editing it in Bitbucket or pasting your configuration in our validation tool here.

Your bitbucket-pipelines.yml configuration does not target the branch you're after

Tips:

If you want to target master, either specify

pipelines:
  default:
    - step:
        script:
          - # do stuff

or

pipelines:
  branches:
    master:
      - step:
          script:
            - # do stuff

 More information in documentation here.

Pipelines has become disabled

You can check this in your Bitbucket repository settings.

Hope this helps!

[Mike Dougherty]

Hello Davina,

I had the same problem this morning. I committed and push some changes to my repo. But the pipeline did not trigger automatically. 

Though when I ran the pipeline manually (select the commit then "Run Pipeline") it worked as expected. So the pipeline, exists and is working properly.

It's just that it did not trigger on the push.

Happy to provide information to the Atlassian team that will help diagnose this is needed. Just let me know.