CODEWITHSUNDEEP
asp.netgitazure
mdominick
mdominick

Reputation: 1319

Git Deployment Succeeds But No Changes

I found myself in the weirdest situation here. I have been deploying to Azure via Git for a while now with no issues. However, I just pushed a fairly large set of changes to Azure got no error but nothing changed...

Tried to push again got "Everything up to date"

So, I logged into the Azure management console and looked under deployments and sure enough the push isn't there.

Suggestions? As an aside, I am not an a Mac and I know there are issues with pushing to Azure from a Mac.

UPDATE: Fixed the issue by deleting and redeployed the Azure instance. Ok for dev not so good for prod.

Upvotes: 0

Views: 839

Answers (2)

James Thurley
James Thurley

Reputation: 2900

I just had the same issue, so I'll post my solution here in this old question in case it helps anyone.

I was posting to my GitHub repository but Azure suddenly wasn't picking it up for deployment any more.

I went into the repository on GitHub, then Settings -> Webhooks and Services, and noticed that the Azure webhook had a little red icon indicating a problem. Clicking on it showed that GitHub was getting a 401 Unauthorised response from Azure.

Then I remembered Azure had sent me an email about a week ago saying my website was going to be moved to a new scale unit and my publishing profile would change. I didn't think much of this at the time as I don't deploy with a publishing profile, but it looks like it also changed my deployment trigger URL.

I updated the GitHub Webhook with the new deployment URL (from the Configure tab of my Azure website) and it all works fine again.

Upvotes: 0

Femaref
Femaref

Reputation: 61497

Did you push to the right remote? It sounds like you have two remotes (you can check with git remote -v) and you are pushing the non-azure one.

Another thing might be the branch, are you on a branch that is not master, but azure expects the deploy to happen on the master branch?

From your comment: The deployment script might not have run. You can either create a dummy commit or force pushing by git push -f to make the remote repository receive the content again.

Upvotes: 1

Related Questions