Webhooks for Codebuild appear to randomly not trigger when code is committed to Bitbucket.

Question

I am trying to trigger 50 test builds to rebuild simultaneously in AWS Codebuild when I change the code in a directory and push it. However, each time I make a change and push to bitbucket, only a portion of the 50 start building. The tests are identical apart from a unique id in the name and they all point to the same code in the same directory. The tests that start building appear to be selected at random, and the total number of tests that successfully start to build appears to be random (22 start 1st commit, 31 start 2nd commit, 27 3rd commit, etc..).

In bitbucket next to the commits, the builds tick mark will say 22/22 passed, 31/31 passed, or 27/27 passed etc... so it seems like an issue with Bitbucket webhooks? But I cannot figure out why.

Patrik S · Accepted Answer

Hello @Ryan Tandy  and welcome to the community!

My understanding is that you have your workspace connected to AWS's CodeBuild using webhooks, so each event that happens in your repository is reported to AWS's Codebuild via a webhook request.

In this case, as you mentioned you have 50 builds to trigger on the AWS side, does each of the build corresponds to a webhook entry on your repository, meaning you would have 50 webhooks, or do you have just one webhook for CodeBuild in your repository? I ask this because in Bitbucket Cloud there's a limit of 50 webhooks in a repository as documented in Manage webhooks.

Also, in order to confirm if the webhook is correctly sent to AWS CodeBuild, you can try enabling the webhook history on the repository in question by navigating to Repository > Repository settings > Webhooks > View requests > Enable History (see Troubleshoot Webhooks)

Once that option is enabled, during the period of 1 week, all the subsequent webhooks will be logged and you should have access to detailed information about the request sent by Bitbucket and the response from the destination server. This can help to troubleshoot if Bitbucket is correctly sending the request and what AWS is returning as a response code.

Thank you, @Ryan Tandy !

Patrik S