Hi Nulab Community,
I’m working on integrating Backlog GIT webhooks with an AWS CI/CD pipeline (using API Gateway, Lambda, and AWS CodePipeline) to automate deployments for a repository with two branches: staging and production. My goal is to trigger separate CodePipeline executions based on push or merge events to these branches. However, I’m facing some challenges and would appreciate your help with the following:
- Webhook Configuration Location
In Backlog’s Project Settings, I see two places to configure webhooks: Git and Integrations. Could someone clarify the difference between these two options? For triggering an AWS CI/CD pipeline on Git push events, which section should I use to set up the webhook URL pointing to my API Gateway endpoint? - Multiple Webhooks for a Single Repository
Is it possible to configure multiple webhooks for a single repository to handle different branches (staging and production) and trigger separate AWS CodePipeline instances? For example, I want a push to the staging branch to trigger a staging pipeline and a push to the production branch to trigger a production pipeline. If this is supported, what are the best practices for setting up and managing multiple webhooks in Backlog?
My setup involves an AWS Lambda function that processes the webhook payload to identify the branch and starts the appropriate CodePipeline. Any advice, examples, or documentation on how to configure Backlog webhooks for this use case would be greatly appreciated!
Thank you