| You can try checking what you put in the "Committers to Ignore" field against the committer in git...make sure you're using the right name, for example using the actual username instead of display name in some instances. FWIW, this is the Bitbucket add-on that is firing the events back to Jenkins, and that's what Jenkins updates: https://marketplace.atlassian.com/plugins/nl.topicus.bitbucket.bitbucket-webhooks/server/overview In short, the Bitbucket Branch Source Plugin in Jenkins updates the webhooks in Bitbucket. When a matching event is figured (see your webhook configuration), it notifies Jenkins by posting content to a URL (can't remember off-hand). This is where you can try to add Jenkins loggers to see what it's getting. Fortunately, since it's receiving data that you don't want, it's easier to dig into than not receiving data that you do want  ...hopefully. My guess is though that it's either a Bitbucket add-on bug or more likely a mismatch between the committers to ignore field and the actual committer id that shows up in the git log |
