Check the logfile for any exceptions or similar.
To be sure that everything is working wellcorrectly, please check the following points:
Enabled Polling SCM is enabled (no schedule is necessary, so it that field can be left empty) Refer to
Check the configured SCM URLs, ; they need to be identical.
Trigger manually the notification (Button called Trigger Jenkins) over the settings page in Bitbucket.
If it doesn't work now, try to unsuccessful, trigger the poll manually with curl or similar tools:
...
curl http://jenkins.com:8080/git/notifyCommit?url=ssh://git@bitbucket.com:7999/eee/repo.git
If it doesn't workthe Jenkins job does not trigger, there is likely a problem with Jenkins.
If it works, check if all hook files are executable /data/repositories//hooks and /data/repositories//hooks/post-receive.d.
If it doesn't work now, try still does not work, Enable the debug output and attempt to get some debug information. To achieve it, you can simply Enable the debug output.
Enable the debug output
There are two possibilitiesmethods to enable the debug output: activate the general debug output or just one of the necessary classes:
General debug
...
You can also examine the Git Polling Log in on the Job configuration page. The Git Plugin only polls the repository if the URL and the branch match one of the jobs' configurations (all jobs using the Git Plugin are given the opportunity allowed to poll if they match the request sent by Bitbucket).
...