Closed davelosert closed 6 years ago
Alright I solved it myself. Actually the Post Webhooks Plugin has a very misleading wording: Pull request updated means: It was edited in the UI of Bitbucket itself (e.g. a new title was set).
The right trigger is actually called Pull request re-scoped - this will trigger a rebuild on new commits.
When hitting the /bitbucket-scmsource-hook/notify Endpoint after a pull request update, the pull request is currenty not built in Jenkins, but there is also no error. The endpoint returns with a 200, but the Pull-Request itself does not get rebuilt. I tried the endpoint manually with Postman with the same result.
I am using the Post Webhooks for Bitbucket Plugin and selected the Pull Request Events Pull request created and Pull request updated.
The Repository-Event on push works just fine and always triggers my branch build correctly.
My Goal: Whenever there is an update to a pull request (new commits added) I want the pipeline to rebuild.
Is this even an intended Feature?