Push Hooks Internal Error Net::ReadTimeout while integrating to Azure

On GitLab.com, webhooks are set to time out after 10 seconds. This is quite short and regularly fails when integrating against Azure. Perhaps we could increase the timeout to 15, 30, or 60 seconds instead?

Original description

Summary

This bug happens on GitLab.com

We have a number of integrations set up as Push Hooks on release branches, for our repository. Most times these fail with an internal error, with a Net::ReadTimeout in red when clicking on the details.

Steps to reproduce

Steps to reproduce. Push or Rebase onto one of our release branches, 8 times out of 10 fails with a timeout.
Going into 'View Details' and clicking "Resend Request" usually works after one or two tries, as can be seen in the screenshot.

Example Project

(If possible, please create an example project here on GitLab.com that exhibits the problematic behavior, and link to it here in the bug report)

(If you are using an older version of GitLab, this will also determine whether the bug is fixed in a more recent version)

What is the current bug behavior?

Push Hook Fails with Internal Error Net::ReadTimeout

What is the expected correct behavior?

Successful push to configured url in push hook

Relevant logs and/or screenshots

image (Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's tough[ to read otherwise.)]

Output of checks

This bug happens on GitLab.com)

(If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com)

Results of GitLab environment info

Expand for output related to GitLab environment info 
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:env:info)


(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production)

Possible fixes

Maybe a configurable timeout on the push hook?

Edited by Nick Thomas