The build was not triggered for a particular commit

Summary

This article will give troubleshooting tips and discuss possible causes when the build was not triggered for a particular commit with Bitbucket Cloud Pipelines

Solution

Possible causes:

• There is no definition on the bitbucket-pipelines.yml file that matches the branch that is receiving a Git push. It's also important to double-check the bitbucket-pipelines.yml file for spelling mistakes, as the branch name in the bitbucket-pipelines.yml file needs to match the name of the branch on the Bitbucket repository exactly for the build to be triggered.

• The push has more than 5 references(branches, tags, bookmarks)

• The push contained multiple commits at once. Pipelines will only trigger builds for the HEAD of the current Git push, meaning that, if a user pushes there commits together, only the latest will trigger a build.

• The webhook size (based on the commit size) is more than 256Kb. The commit message size can be checked from the Bitbucket UI.

Troubleshooting Steps:

Did the push have more than 5 references or was the webhook larger than 256Kb?

YES

• Push has more than 5 references

  • Pipelines will not run a build if it has more than 5 references on the same push (branches, tags, bookmarks) as documented on the Limitations of Bitbucket Pipelines page.

  • If you want, you can manually run the build that did not automatically trigger by:

    • Running a pipeline manually from the Branches view

    • Running a pipeline manually from the Commits view

    • Running a pipeline manually from the Pipelines page section

    For information on manually running pipelines, see: Pipeline triggers.

  • To prevent future builds from not triggering, reduce the number of references (branches, tags, bookmarks) in a single push.

• Webhook size is larger than 256kb

  • If the commit message is too large and it is not supported by Bitbucket as mentioned on the Limitations of Bitbucket Pipelines page, the result can be a webhook that is larger than the 256Kb limit.

  • If you want, you can manually run the build that did not automatically trigger by:

    • Running a pipeline manually from the Branches view

    • Running a pipeline manually from the Commits view

    • Running a pipeline manually from the Pipelines page section

    For information on manually running pipelines, see: Pipeline triggers.

  • To prevent future builds from not triggering, reduce the commit size.

NO

• Raise a Support Ticket and share the commit that didn’t trigger the Pipeline build.