Timeout value is not respected by the Octopus client

[mcasperson]

You can define a timeout in the TFS steps, but when deploying a release this value is not passed to the Octopus client. For example, setting a timeout of 30 minutes will still result in a long deployment failing after 10 minutes, because the Octo.exe --timeout value defaults to 10 minutes.

[johnsimons]

So after some digging around, we cannot do this for the users, see https://github.com/microsoft/azure-pipelines-task-lib/issues/796. However, it is possible to control the timeout and cancel a deployment task by supplying extra octo arguments, here is an example:

So for now I am closing this issue.