search

nightscout / cgm-remote-monitor

nightscout web monitor
GNU Affero General Public License v3.0
2.42k stars 71.77k forks source link

Azure fails to deploy 0.5.1 from github. #248

Closed someoneAnyone closed 9 years ago

someoneAnyone commented 10 years ago

I followed the normal steps of disconnecting source control from Azure and reforked the repo from the source so I can get the new .1 release of cookie monster. When I try to reconnect Azure to github it authenticates ok, but fails during the deployment. Any ideas if its something in the project or on MS' side and does anyone have any contacts to support there... apparently having a free account doesn't entitle you to tech support.

Thanks!

ELUTE commented 10 years ago

Just keep trying. You can try another browser etc. It should eventually deploy.

On Nov 11, 2014, at 2:55 PM, someoneAnyone notifications@github.com wrote:

I followed the normal steps of discounting source control from Azure and reforked the repo from the source so I can get the new .1 release of cookie monster. When I try to reconnect Azure to github it authenticates ok, but fails during the deployment. Any ideas if its something in the project or on MS' side and does anyone have any contacts to support there... apparently having a free account doesn't entitle you to tech support.

Thanks!

— Reply to this email directly or view it on GitHub https://github.com/nightscout/cgm-remote-monitor/issues/248.

bewest commented 10 years ago

Actually, I believe disconnecting and reforking is likely to cause issue at least some of the time, can we remove these recommendations altogether?

The forking and connecting steps should oniy happen once at the very beginning, the need to delete, refork and things should be extremely rare, when the recommendations are followed.

bewest commented 10 years ago

@someoneAnyone can you point out to me where the directions are for disconnecting from Azure?

someoneAnyone commented 10 years ago

@bewest Step 5 at: http://www.nightscout.info/wiki/welcome/how-to-update-to-latest-cgm-remote-monitor-aka-brownie

ELUTE commented 10 years ago

It has been an issue with Azure for the last 2 days. Even when users are not deleting their forks and re-forking. The tool you created is great. We are planning on including that in the instructions once we are ready to go forward with Cookie Monster again.

On Nov 11, 2014, at 3:36 PM, Ben West notifications@github.com wrote:

Actually, I believe disconnecting and reforking is likely to cause issue at least some of the time, can we remove these recommendations altogether?

The forking and connecting steps should oniy happen once at the very beginning, the need to delete, refork and things should be extremely rare, when the recommendations are followed.

— Reply to this email directly or view it on GitHub https://github.com/nightscout/cgm-remote-monitor/issues/248#issuecomment-62616490.

bewest commented 10 years ago

I see. :-) You are very kind... the tool is... ok for now.

someoneAnyone commented 10 years ago

My site is hosed at the moment (left cookie monster running and chewed through my data allotment for the day), but I was able to relink Azue with the project, I think. I got the following warning after it completed.

Could not retrieve the CDN endpoints in subscription with ID '717fc908-fca7-4c67-adca-3d087681080b'.

Any ideas what this is?

dduugg commented 10 years ago

Azure's CDN endpoints issue seems to be a common one:

http://stackoverflow.com/questions/20793209/could-not-retrieve-the-cdn-endpoints-in-subscription-with-id

Still no answer though :(