Hi Trung, thanks for reporting this. We are aware of the issue and are looking at solutions.
In the meantime, there is a workaround to this issue:
- Create your pipelines project as normal.
- Within that project, start a build of that project and wait for it to resolve (it does not need to be successful, just running it is enough)
- Once completed, click "configure" to go back to the project configuration
- Ensure the "Bitbucket Server trigger build after push" build trigger is checked
- Save the project configuration
This should trigger the webhook to be created in Bitbucket Server.
If you're having trouble with this solution, you can also create a webhook manually in your repository settings- create it with the URL `http://<jenkins-instance-url>/bitbucket-server-webhook/trigger`, with the secret field empty, and with the "push" event checked.
Feel free to reach out if you have any other issues.
Hi Trung, thanks for reporting this. We are aware of the issue and are looking at solutions.
In the meantime, there is a workaround to this issue:
This should trigger the webhook to be created in Bitbucket Server.
If you're having trouble with this solution, you can also create a webhook manually in your repository settings- create it with the URL `http://<jenkins-instance-url>/bitbucket-server-webhook/trigger`, with the secret field empty, and with the "push" event checked.
Feel free to reach out if you have any other issues.