You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I want to receive webhooks on our own event infra when our BitBucket Pipelines are running. We've enabled the webhooks in the repo settings and selected build start and build update. But the webhooks won't fire.
I've enabled the call history, and no calls show up. We are running our own BitBucket runners and they properly run our BB pipelines.
Does anybody has this problem? Thanks!
The webhook with these triggers should get triggered when a commit's build status is created or updated, so the page to check that would be the Commits page of the repo:
I tried to reproduce this issue with a self-hosted Linux Docker runner, but I haven't been able to. If you provide also the following info, I can try to reproduce a use case similar to yours:
Yes, on the commits page we have the build status, like so:
We run builds at push actions and run builds every night by schedule. No requests appear in at the webhooks, even after clicking "Load new requests":
This is our setup now:
Thanks for your help!
Thank you for the info. The image you specify in your bitbucket-pipelines.yml file shouldn't make a difference. When the build finishes, it's the runner that updates the build status of the commit (with failed or successful status) with an API call. After the commit's build status is created, it's Bitbucket that should trigger the webhook.
I still cannot reproduce this issue with a setup similar to yours, and since the commit statuses are there, I can't think of a reason why the webhook shows no requests.
I would suggest creating a ticket with the support team; if we have a support ticket, the engineer working on it will be able to check the repo's configuration and our logs to investigate this further.
You can create a ticket via https://support.atlassian.com/contact/#/, in "What can we help you with?" select "Technical issues and bugs" and then Bitbucket Cloud as product. When you are asked to provide the workspace URL, please make sure you enter the URL of the workspace that is on a paid billing plan to proceed with ticket creation.
Please feel free to let me know if you have any questions!
These events are only triggered at the end of the build. So, if you want to know when the pipeline is running you probably need to subscribe to events that actually trigger your build like 'repo:push' and 'pullrequest:created'. Or alternatively, have the pipeline trigger your webhook.
Having said that, it should still have triggered those events after the build. Did it create a build status on the PR/commit?
In this case I want to see if pipelines succeed of fail. If I handle the webhooks in my pipeline steps, it's possible that they never fire.
I agree that they should fire on "Build status created" and "Build status created". In my repo I sure see the build statusses:
That's odd - I've created some dummy webhooks for these events in a test repo and they are being triggered correctly. It's not using runners though, not sure if this would affect in this case.