This issue has been closed due to inactivity. If you continue to see problems, please reopen or create a new issue.

Last saturday dec. 14, 2014, our deployment is working fine, but after that it is failing, I can see a log inside azure deployment tab, that says "you may increase SCM_COMMAND_IDLE_TIMEOUT setting to solve the issue". did increased the SCM_COMMAND_IDLE_TIMEOUT but still same result
Any solution?

Has there been any update to this? Currently continuous deployment to Azure is broken from Bitbucket commits.

@nvenegas

it relied on having the username:password@ part in the URL.

Like Justin, I am passing in the username:password@ format in my POST url. However, it appears bitbucket is not sending the credentials correctly. I can take this exact same url and curl it or use github's service hook and it'll authenticate correctly.

@davidebbo we previously sent no header for our POST service; it relied on having the username:password@ part in the URL.

@nicolasvanegas30 ah, that probably explains this issue.

Though I'm not sure I understand the change. The Azure service uses basic auth, so you must have been sending the right auth header before or it would have failed, no?

My fix to sent basic auth headers may have broken automated deployments from Windows Azure.

I've reverted my change so that I can investigate.