Page Comparison

Check If the Jenkins job does not trigger, start by checking the logfile for any exceptions.

To be sure Next, ensure everything is working correctly, check confirm the following points:

• Polling SCM is enabled (no schedule is necessary, so that field can be left empty) Refer to Git plugin for instructions.

• Check the configured SCM URLs; they need to be identical.

• Trigger manually the notification (Button called Trigger Jenkins) over the settings page in BitbucketTest Configuration) from any Webhook to Jenkins for Bitbucket Server tab.

If unsuccessful, trigger the poll manually with curl or similar tools:

curl -v http://<Jenkins URL>/git/notifyCommit?url=<SCM URL>

curl http://jenkins.com:8080/git/notifyCommit?url=ssh://git@bitbucket.com:7999/eee/repo.git

If the 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 still does not work, Enable the debug output and attempt to get some debug information.

...

Jenkins has built-in logging capabilities. You can create a logger and see what Jenkins receives:

1. Go

...

1. to http://jenkins/log/new

2. Set the name of the new log recorder: git

3. Click OK.

4. Add a Logger: hudson.plugins.git

5. Click Save.

Now click Click Trigger Build to trigger a build from Bitbucket. Go to the logger page (http://jenkins/log/git) and reload the page. You should now see what the Jenkins Git Plugin received. It should look like this:

...