Settings and activity
1 result found
Until we implement this feature, the work around would be to monitor the deployment using the API and cancel it if a timeout has been reached.
I have written up a script (https://octopus.com/blog/automating-octopus-with-azure-functions) that retrieves all running deployments for a project and cancels it if:
- it has been running for more that 30 minutes
- the first step has been running fro more than 20 minutes
- the first step has not output any logs in 5 minutes
This can run as a scheduled task. Alternatively you can use the subscriptions feature to kick off a piece of code (eg Azure function) that does this polling, as described in this blog post: https://octopus.com/blog/automating-octopus-with-azure-functions
— Robert W
An error occurred while saving the commentKyle Carmitchel supported this idea ·
I'm having an issue with a downstream system (functional testing tool) that is itself hanging, but unfortunately the state in which its hanging is causing Octopus to spin on the step talking to it indefinitely. This will then cause all deployments behind it to back up and also hang indefinitely.
If I could simply specify a timeout on the step talking to the testing tool, where if it takes longer than X minutes, simply cancel and fail the step, it would be a huge help to us.