Problem Definition

We use push webhook to trigger a Jenkins job. Currently, the webhook is triggered for any changes in a repository including Adding and Deleting branches. As a system admin, I want to trigger the job ONLY when a user modifies a branch. Adding or Deleting a branch should not trigger a Jenkins job.

We don't want to use  Atlassian supported Jenkins integration for Bitbucket Server as we may not use Jenkins in other projects.

Use-Case Scenario

• BitBucket sends one PUSH webhook on Branch Modified, Added and Deleted, and on Tag Added and Deleted.
• Almost 100% of code changes required, at minimum, an automation process to make sure the build is not broken.
• This scenario is triggered by a branch modification or by Tag addition (PUSH command in GIT).
• For a branch - When a branch is added or deleted the automation process has nothing to do - there is no reason to test a new branch and there is no branch to test when it has been deleted.
• For a tag - When a tag deleted the automation process has e nothing to do - there is no reason to test a tag when it has been deleted.
• The problem is that the Jenkins jobs are triggering anyway and I need to add filtering code and let go only branches changes and new tags.
• There are a lot of new branches and a lot of deleted branches so Jenkins is occupied for nothing and Jobs# sequence with unreasonable holes.
• We would like to have a separate hook for every event and let the customer decide whether to use it or not. Just like you did in commit comment and in PR events.