Closed hajekj closed 9 years ago
It appears that the SCM_COMMAND_IDLE_TIMEOUT setting in .deployment file solved the issue. Maybe you could add it into the documentation or something maybe?
Thanks for reporting and finding this issue... would you like to update the documentation so you are recognized for your contribution?
Thank you, it is nice of you. I will try to have it added by tomorrow.
I think there is a better approach. As you can read in documentation of the SCM_COMMAND_IDLE_TIMEOUT setting:
...it's allowed to run for up to 60 seconds without producing any output. ...
And the key is, without producing any output. I think that is better not to use the option --no-progress
so you kill two problems, the command don't timeout and you can also see the log of what happened (that is also good).
And sorry for commenting this closed issue but I think it's something to get in mind.
When deploying the example source code from GitHub, I end up getting following error (WAWS Composer site extension enabled):
Another useful information could be probably Ran For: 400 seconds This seems to me like composer is timing out - possibly by changing the Kudu timeout setting SCM_COMMAND_IDLE_TIMEOUT=600 (as per here), but I haven't tested this yet.
Could you look into this please?