Skip to content

Settings and activity

1 result found

  1. 67 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    11 comments  ·  Product Feedback » Deployments  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    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 comment
    DG commented  · 

    Still not a feature at this time and Octopus said they just don't see it ever happening because of Dev time constraints and priorities. This is a make or break feature for my company as it leaves several people sitting and waiting for a long running step that is failing. This costs way too much time, which is money, frustration, and unreliability to perform smooth rollouts with Octopus. We are considering not using Octopus anymore because of this unreliability alone and we've invested a lot into it already. Even after the huge time and financial investment it's not worth the headache and unpredictability
    https://help.octopus.com/t/stop-current-step-and-force-fail/23866/4

    DG supported this idea  ·