3

I set up git continuous deployment with bitbucket on my Azure website according to this blogpost

I go through all steps without any problems but when I git push to bitbucket no Azure deployment happens...

If I push to my azure git url, deployment works as usual.

Anybody else that have had this problem?

Thanks!

Improve this question
1
  • What error do you get when it fails to push? Commented Dec 28, 2012 at 12:21

3 Answers 3

Reset to default
7

Yesterday we deployed to bitbucket.org a change to send the Authorization header with our POST service that may have broken our integration with Windows Azure.

I've rolled back the change so that we can investigate.

Does it work for you now?

Improve this answer
Sign up to request clarification or add additional context in comments.

2 Comments

Oh that's interesting. That probably explains social.msdn.microsoft.com/Forums/en-US/azuregit/thread/…! Would you mind commenting there as well with more info? Thanks!
Hi @nicolasv have you by any chance re-applied this change recently? I last did a deployment on 17th Jan and it worked, now I have tried one today (22nd Jan) and Azure is not picking it up. If I push to Azure from git it works, so I suspect it is a BitBucket issue.
0

Did you set bitbucket deployment up after pushing directly to your git repo on Azure? You'll need to FTP in and empty the deployments folder and then refresh the deployment tab on the portal. You'll then be able to link your bitbucket account again and it should just work then

Improve this answer

1 Comment

tried this, and it didn't solve the issue. Though i noticed that for private/public repos where i was admin, integration happened smoothly. It's only for repos where i had only read-write-access that i couldn't setup the deployment. Actually, to test this hypothesis, i made a fork of a repo where i had only rw-access (in the fork, i'd be admin automatically), and then tried setting up deployment with this fork. It worked fine!
0

This might not be the solution in all cases, but for me it's one of the hypotheses I've tested and found true:

I noticed that for private/public repos where I was admin, integration happened smoothly. It's only for repos where I had only read-write-access that I couldn't setup the deployment from version control (that is for Bitbucket and Azure Websites).

Actually, to test this hypothesis, I made a fork of a repo where I have only rw-access (in the fork, am automatically made admin), and then tried setting up deployment with this fork. It worked fine!

Note that for all the repositories I tried linking to (whether private or not, and whether the linking worked or not) I had read-write access. Though, I believe the ultimate setup should only need read-access to a repo. Am yet to isolate the actual problem...

Improve this answer

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.