-
Bug
-
Resolution: Duplicate
-
Minor
-
None
-
Jenkins 2.289.2
Bitbucket server v7.17.2
Dear Jenknis team,
We fail to setup automatic build triggering in Jenkins using Bitbucket webhooks.
The Bitbucket Server Integration plugin is installed and configured, following the official integration manual
The triggering method is configured via Bitbucket webhook trigger. The webhook itself is successfully created in Bitbucket and build status is updated as well (builds can be invoked manually from Bitbucket and complete successfully in Jenkins).
Triggering builds after commit / push / merge is not working though, even when the webhook is active and the latest responses are: http code 200 (success).
Any idea how we can make it work? Please refer to the screenshots as well.
The Jenkins log file reports:
INFO c.a.b.j.i.t.BitbucketWebhookConsumer#lambda$hasMatchingRepository$6: Base URL of incoming repository selflink - https://xxxxxxxxxx and bitbucket server configured URL - http://xxxxxxxxxx:7991 seems to be be different
Thank you!
- duplicates
-
-
- Open
-
[JENKINS-68496] Build trigger using Bitbucket webhook not working
Andrey Tsolev
created issue -
Andrey Tsolev
made changes -
| Description |
Original:
Dear Jenknis team,
We fail to setup automatic build triggering in Jenkins using Bitbucket webhooks. The Bitbucket Server Integration plugin is installed and configured, following [the official integration manual|https://plugins.jenkins.io/atlassian-bitbucket-server-integration/] The triggering method is configured via Bitbucket webhook trigger. The trigger itself is successfully created in Bitbucket and build status is updated as well (builds can be invoked manually from Bitbucket and complete successfully in Jenkins). Triggering builds after commit / push / merge is not working though, even when the webhook is active and the latest responses are: http code 200 (success). Any idea how we can make it work? Please refer to the screenshots as well. The Jenkins log file reports: INFO c.a.b.j.i.t.BitbucketWebhookConsumer#lambda$hasMatchingRepository$6: Base URL of incoming repository selflink - [https://xxxxxxxxxx] and bitbucket server configured URL - [http://xxxxxxxxxx:7991] seems to be be different Thank you! |
New:
Dear Jenknis team,
We fail to setup automatic build triggering in Jenkins using Bitbucket webhooks. The Bitbucket Server Integration plugin is installed and configured, following [the official integration manual|https://plugins.jenkins.io/atlassian-bitbucket-server-integration/] The triggering method is configured via Bitbucket webhook trigger. The webhook itself is successfully created in Bitbucket and build status is updated as well (builds can be invoked manually from Bitbucket and complete successfully in Jenkins). Triggering builds after commit / push / merge is not working though, even when the webhook is active and the latest responses are: http code 200 (success). Any idea how we can make it work? Please refer to the screenshots as well. The Jenkins log file reports: INFO c.a.b.j.i.t.BitbucketWebhookConsumer#lambda$hasMatchingRepository$6: Base URL of incoming repository selflink - [https://xxxxxxxxxx|https://xxxxxxxxxx/] and bitbucket server configured URL - [http://xxxxxxxxxx:7991|http://xxxxxxxxxx:7991/] seems to be be different Thank you! |
Andrey Tsolev
made changes -
| Component/s | New: atlassian-bitbucket-server-integration-plugin [ 25721 ] | |
| Component/s | Original: bitbucket-branch-source-plugin [ 21428 ] | |
| Component/s | Original: bitbucket-plugin [ 18755 ] | |
| Component/s | Original: bitbucket-push-and-pull-request-plugin [ 24647 ] |
Andrey Tsolev
made changes -
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
| Link | New: This issue duplicates JENKINS-68589 [ JENKINS-68589 ] |
| Resolution | New: Duplicate [ 3 ] | |
| Status | Original: In Progress [ 3 ] | New: Closed [ 6 ] |