If I trigger the webhook manually it takes awhile to finish but it does finish. When the webhook is triggered via a push to bitbucket I get a timeout error. How can I increase the time allowed for the webhook to finish so I don't get this error?
Is this for Bitbucket Server (hosted on your premises) or Bitbucket Cloud (accessible at bitbucket.org)?
If that's about Bitbucket Server, you could try increasing this timeout:
The default is 10000 milliseconds. See Bitbucket Server config properties for more details.
However, I would try to troubleshoot why the hook is timing out (i.e. what exactly is taking a long time to complete). The setting above only increases the connection timeout.
Caterina - Atlassian Support
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs