As reported by our user, the plugin bitbucket server webhook to jenkins was used in order for their jenkins builds to spawn when a pull request is created or push new changes to a pull request. Though recently, new builds are no longer spawned when new changes are pushed to pull request branch. The initial build upon creation still works but nothing happens when new codes are pushed. This could be hardly blamed to jenkins configuration as it uses the same buildWithParameters url whether the PR is created or updated.
Please note also that it does fire when the user adds a reviewer but not when he push changes to the branch. An exact opposite of what the user would prefer.
Hi,
As reported by our user, the plugin bitbucket server webhook to jenkins was used in order for their jenkins builds to spawn when a pull request is created or push new changes to a pull request. Though recently, new builds are no longer spawned when new changes are pushed to pull request branch. The initial build upon creation still works but nothing happens when new codes are pushed. This could be hardly blamed to jenkins configuration as it uses the same buildWithParameters url whether the PR is created or updated.
Please note also that it does fire when the user adds a reviewer but not when he push changes to the branch. An exact opposite of what the user would prefer.