Outbound Webhooks Improvements
S
Suyan Suyanwar
Hi Henna Abbas, I'm Suyanwar. Mobile architect at Amarbank. I want to ask about the webhook scheme from Bitbucket into Circle CI. We know that when we setup project repository in circle ci, connecting to branch that has config.yml file and configuration, its mean we create a webhook from bitbucket to circle ci using this hook: https://circleci.com/hooks/bitbucket. The webhook configuration triggered using push event, pull request created, updated, merged and declined event by default. On circle ci we have this feature in project setting: Only build pull requests -> By default, we will build all the commits for this project. Once turned on, we will only build branches that have associated pull requests open. If we enabled it we cannot run workflow on push event. And vice versa, if we turned it off, we cannot run workflow on pull request event. As per now i have workflow that should be run on push event but not on pull request event and I also have workflow that should be run on pull request event only. Then because of the limitation between circle ci X bitbucket. I use n8n as a hook transformer. So I create bitbucket webhook on pull request event to trigger n8n workflow to transform json data and init circle ci pipeline by API. I know i can use bitbucket pipeline itself to create circle ci pipeline by API. But my question is, can the support is from circle ci side since circle ci already has generic webhook: https://circleci.com/hooks/bitbucket. So i can auto differentiate when pipeline init is based on push event or pull request event. Because circle ci web dashboard already know Trigger event is based on push event or else. Or do I have lack of knowledge to use the circle ci feature?