Settings and activity
-
65 votes
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 minutesThis 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
Bryan Roth
supported this idea
·
An error occurred while saving the comment -
362 votesUnder Consideration · 40 comments · Product Feedback » Deployments · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment Bryan Roth
commented
Any update?
An error occurred while saving the comment Bryan Roth
commented
Any update?
Bryan Roth
supported this idea
·
An error occurred while saving the comment Bryan Roth
commented
I see the status has changed to 'Planned' as of June 26, 2019. Does this mean there has been a set back since this was 'Started' back in January 2018? Are there any updates on this feature?
An error occurred while saving the comment Bryan Roth
commented
Any updates?
-
39 votesBryan Roth
supported this idea
·
-
209 votesBryan Roth
supported this idea
·
An error occurred while saving the comment Bryan Roth
commented
This would be very useful. I've noticed built-in Octopus steps failing because of a locked file, and simply retrying that step often succeeds. It would be nice to have an option to retry a step if a failure occurs up to a certain amount of retries.
I know it's possible to bake in retry functionality into script steps or step templates that you create.
Any update on this?