Deploy to Azure failed

[miletine]

Please include the following information with your bug report:
Is this a new bug with the latest release, have you seen this earlier?

I performed the auto update of the fork to merge all to bring myself up to the latest version.
Which device / browser version was used to reproduce the bug?
The azure portal

Does this happen every time you launch Nightscout, or sometimes?

Site is down. Won't start.

Steps how to reproduce (if you can’t reproduce the issue, please don’t report the issue / if we can't reproduce the bug, we can't fix)

The sync failed so I then followed the "update my fork troubleshooting" to disconnect from GitHub and reconnect. Looking at the change summary of changes I updated the application settings to from WEBSITE_NODE_DEFAULT_VERSION 0.10.32 to 8.9.0

This removed some of the error messages. I can see that it still chose a higher version for node (8.9.4 instead of 8.9.0) but the change log showed that NPM was deliverately depreciated.
How do I force it to chose 5.2.0 ? From the messages it seems that the depreciated commands probably available in 5.2.0 are not available in 5.3.0

Please include 1 or more screenshots of the issue appearing, ideally with an annotation on what's wrong

Deployment Details:

Status Failed
Triggered By GitHub
Author miletine
Ran For 1350 seconds
Reason
Merge pull request #3 from nightscout/master Changed to G5
Deploy To miletine

	Sat 03/10	Updating submodules.
	Sat 03/10	Preparing deployment for commit id 'eae0bba12e'.
	Sat 03/10	Running custom deployment command...
	Sat 03/10	Running deployment command...	View Log

Delployment Log

Command: bash deploy.sh
Handling node.js deployment.
KuduSync.NET from: 'D:\home\site\repository' to: 'D:\home\site\wwwroot'
Copying file: 'scm-commit-id.json'
Using start-up script server.js from package.json.
Node.js versions available on the platform are: 0.6.20, 0.8.2, 0.8.19, 0.8.26, 0.8.27, 0.8.28, 0.10.5, 0.10.18, 0.10.21, 0.10.24, 0.10.26, 0.10.28, 0.10.29, 0.10.31, 0.10.32, 0.10.40, 0.12.0, 0.12.2, 0.12.3, 0.12.6, 4.0.0, 4.1.0, 4.1.2, 4.2.1, 4.2.2, 4.2.3, 4.2.4, 4.3.0, 4.3.2, 4.4.0, 4.4.1, 4.4.6, 4.4.7, 4.5.0, 4.6.0, 4.6.1, 4.8.4, 5.0.0, 5.1.1, 5.3.0, 5.4.0, 5.5.0, 5.6.0, 5.7.0, 5.7.1, 5.8.0, 5.9.1, 6.0.0, 6.1.0, 6.2.2, 6.3.0, 6.5.0, 6.6.0, 6.7.0, 6.9.0, 6.9.1, 6.9.2, 6.9.4, 6.9.5, 6.10.0, 6.10.3, 6.11.1, 6.11.2, 6.11.5, 6.12.2, 6.12.3, 7.0.0, 7.1.0, 7.2.0, 7.3.0, 7.4.0, 7.5.0, 7.6.0, 7.7.0, 7.7.4, 7.10.0, 7.10.1, 8.0.0, 8.1.4, 8.4.0, 8.5.0, 8.7.0, 8.8.0, 8.8.1, 8.9.0, 8.9.3, 8.9.4.
Selected node.js version 8.9.4. Use package.json file to choose a different version.
Selected npm version 5.3.0
Updating iisnode.yml at D:\home\site\wwwroot\iisnode.yml
npm WARN invalid config scripts-prepend-node-path="--production"
npm WARN deprecated [email protected]: Use uuid module instead
Thread was being aborted.
Thread was being aborted.

[miletine]

I just noticed that this is very similar to the much earlier hosting-azure issue. I don't know how to add the label.

[miletine]

Similar to earlier post. After 3 hours another attempt at "Sync" now works.