Hello,

I am reaching out from Prudential USA company.

Issue Summary:

The plugin we use for webhook setup is called "bitbucket-server-integration" and that was also upgraded from 2.1.2v to 3.3.2v as part of Jenkins upgrade.

• https://plugins.jenkins.io/atlassian-bitbucket-server-integration/{^}!https://confluence.prudential.com/images/icons/linkext7.gif

Since the plugin got upgraded, the previously working webhook stopped working and any new commits to repo stopped triggering the Jenkins pipelines. We can see 200 response in webhook log but it still didn't fire and didn't trigger Jenkins Job.

The work around we implemented is:

We manually enabled the below option in Jenkins and then a new webhook got created by Jenkins in bitbucket with different name but same webhook URL and then the connection with Jenkins and Bitbucket will be reestablished.

This fixed the webhook issue and pipelines got triggered whenever there is a new commit to repo. 

Note: Now, after implementing this fix, there are two webhooks in the repo, although we noticed having two webhooks didn't cause any issue, we went ahead and deleted the older webhook (the one which shows NEVER FIRED) which is not needed anymore.

Questions:

1. Why the webhook stopped working after the plugin upgrade, is this issue related to https://issues.jenkins.io/browse/JENKINS-63071?
2. The workaround we found is going to each pipeline and manually checking the checkbox option, but there are like more than 500 pipelines that we know and there may be more that we don't know. So, its not a easy and smart approach. How can we identify all the pipelines that are affected and fix them. Do you have any better solution?

Please let me know if you need any further details. Looking forward to your response.

Thank you for looking into this.

Karra