title: Google cloud container builder not always triggering from bitbucket
body: <p>I have build triggers set up in the Google Cloud Container Builder that are set to trigger on specific branches and use the cloudbuild.yml config in the repo. For about the first day that I pushed commits to any of these branches, it triggered a container build and completed successfully. Since then, the triggers have only worked intermittently.</p>
  
  <p>Sometimes Google Cloud Container Builder doesn't detect the commit at all (I have checked the commit is in bitbucket and the commit is on the right branch). At that point, I've tried manually triggering a build through the google console, but it <strong>uses the older commit</strong> that it last built on, not the latest commit. So then I will try to push small changes from the repo or do an empty commit.</p>
  
  <p>Sometimes that triggers the build, sometimes not. The interesting thing is that when the build finally triggers on a branch after a while, it will trigger builds on the other branches if they have a recent commit that hasn't been built.</p>
  
  <p>I have no idea how to resolve this. Has anyone experienced a similar problem?</p>
  
  <p><strong>UPDATE:</strong></p>
  
  <p>I solved my problem. I originally added each bitbucket repository to the Source Repositories in Google Cloud. After that, I added the build triggers for each of those repos in the Container Registry. When adding the trigger, I had to go through the same process of connecting to the repositories in Bitbucket as I was taken through with adding the source repositories. I later realized that it had created a separate connection in the Source Repositories section for each of these repos automatically. So I had two connections to each repo in bitbucket listed in the Source Repositories. Once I deleted the duplicates, the triggers started working consistently.</p>
  
  <p>In summary, make sure you don't have any duplicate connections in the Source Repository.</p>