The Bitbucket notification is being received, but the build is not being triggered because it thinks nothing has changed.

Started on Aug 10, 2017 8:48:14 PM
Using strategy: Default
[poll] Last Built Revision: Revision c23a89b67fc218799b3c96b1903a3d2c2a3bc774 (refs/remotes/origin/master)
using GIT_SSH to set credentials amplify-jenkins bitbucket user
> git ls-remote -h git@bitbucket.org:amplify-learning/breaker-panel.git # timeout=10
Found 2 remote heads on git@bitbucket.org:amplify-learning/breaker-panel.git
Using strategy: Default
[poll] Last Built Revision: Revision c23a89b67fc218799b3c96b1903a3d2c2a3bc774 (refs/remotes/origin/master)
using GIT_SSH to set credentials amplify-jenkins bitbucket user
> git ls-remote -h git@bitbucket.org:amplify-learning/breaker-panel.git # timeout=10
Found 2 remote heads on git@bitbucket.org:amplify-learning/breaker-panel.git
Done. Took 1 sec
No changes

Despite it receiving the notification that only happens on a change, it still thinks nothing has changed.

Some things I've noticed that seem odd:

• The following line (latest remote head) is present in the Bitbucket hook log when the build is triggered successfully, but not when the build is not triggered

  [poll] Latest remote head revision on refs/heads/build_work is: ac6345ae8577950285f96d70a3cff907b48cbd28

   

• I only have the job set to keep 10 builds, but of those 10 the builds that triggered successfully show there are 3 remote heads in the repo whereas when the job does not trigger it shows there are 2 remote heads.  I have other jobs that work that have more than 2 remote heads also.